Standardize Member Variable naming conventions #56
Labels
No labels
Alpha Release Requirement
Bugfix
Demo Target
Documentation
Major Feature
Minor Feature
priority:tier1-active
priority:tier2-foundation
priority:tier3-future
priority:tier4-deferred
Refactoring & Cleanup
system:animation
system:documentation
system:grid
system:input
system:performance
system:procgen
system:python-binding
system:rendering
system:ui-hierarchy
Tiny Feature
workflow:blocked
workflow:needs-benchmark
workflow:needs-documentation
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Blocks
#31
__repr__ displays match the getsetter member names
john/McRogueFace
Reference
john/McRogueFace#56
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
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?
37 refactor: make sure all UIDrawables use consistent member names for fill_color, outline_color, position, size, etc; [depends on RAII] [depends on standardize vector handling] [depends on standardize color handling]
Depends on:
While we're at it, make the C++ and Python variables identical, or formulaic. Python has some
getsetvariables that are not actually in C++, but it should be clear what they derive fromUI.hinto respective class files #43https://gamedev.ffwf.net/gitea/john/McRogueFace/issues/18#issuecomment-354
Time to pay the piper...
__repr__displays match the getsetter member namesMust have caught this stuff elsewhere: there was no inconsistency left when I went to work on it.