Standardize Vector Handling #13
Labels
No Label
Alpha Release Requirement
Bugfix
Demo Target
Documentation
Major Feature
Minor Feature
Refactoring & Cleanup
Tiny Feature
No Milestone
No project
No Assignees
1 Participants
Notifications
Total Time Spent: 1 hour 14 minutes
Due Date
john
1 hour 14 minutes
No due date set.
Dependencies
No dependencies set.
Reference: john/McRogueFace#13
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
notes say:
17 feat: standardize vector handling: 2-tuple or 2 member lists, any mix of ints or floats; or (new) Vector object [depend on SFML module feature]
This issue is for a single method to take a PyObject* of any of the above and return a mcrfpy.Vector2 (or sfml::Vector2f wrapper, if possible)
Once the method is available, every widget that uses vectors (Frame, Caption, Sprite, Grid) needs to use the standardized method.
Goal: Speed. Copy
PyColor
for the structure of this object.1c12e8719c
Gotta go fast - got it to build, got an example position from a UIDrawable.
Can't figure out why my init func isn't working, which means the mcrfpy.Color init function is probably undertested.
Coding sporadically over the morning & afternoon; made some commits before errands.
This issue will now be closed. Here's the salient portion:
There is more work to do in the init methods of the UIDrawables, but the intention with the tuple versions of Vector and Color means that the argument should just be passed to PyVector's / PyColor's constructor. If it fails, then UIDrawable init should also fail.
That refactor belongs to the UI.h breakup story, #43.