Sonkun/python-sfml2 — pull request #9 by aspidites (2012-06-21 09:57:32+00:00)
Title: System fixes

- Rewrote Vector* constructors:

v = sf.Vector2() # constructs a (0, 0) vector as usual
v.x, v.y = (10, 20) # assign x and y values as usual
v2 = sf.Vector2(v) # constructs a (10, 20) vector from an existing vector2
v3 = sf.Vector3(10, 10, 10) # construct a (10, 10, 10) vector as usual
v4 = sf.Vector2(v3) # construct a (10, 10) vector from an existing vector3

If for some reason, it was common or expected behavior to be able to assign a vector to another vector's x (multi-dimentional vectors), let me know. Otherwise, this can still be accomplished as follows:

v = sf.Vector2()
v.x, v.y = sf.Vector(2, 2), sf.Vector(4, 4)

- copy now works property
Before, trying to do `vector.copy()` or `copy(vector)` would result in a (None, None) or (0, 0) vector. I've fixed this