Standardize Member Variable naming conventions #56
			
				
			
		
		
		
	
	
		Labels
		
	
	
	
	No Label
	
		
			
	
	
	Alpha Release Requirement
		
			Bugfix
		
			Demo Target
		
			Documentation
		
			Major Feature
		
			Minor Feature
		
			priority:tier1-active
		
			priority:tier2-foundation
		
			priority:tier3-future
		
			Refactoring & Cleanup
		
			system:animation
		
			system:documentation
		
			system:grid
		
			system:input
		
			system:performance
		
			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 Participants
		
	
	
		
		
			Notifications
			
				
			
		
	
	
		
		
	
	
	Due Date
	No due date set.
			
			
				
					Blocks
				
				
					
						
							
								
							
						
					
					
				
			
			
			
		
		
	
	
	
								
									#31 `__repr__` displays match the getsetter member names
								
								
							
									john/McRogueFace
								
							
			Reference: john/McRogueFace#56
			
		
	
		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?
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 from#18 (comment)
Time to pay the piper...
Must have caught this stuff elsewhere: there was no inconsistency left when I went to work on it.