Property access instead of getters/setters

tobspr · December 9, 2015, 6:38pm

wezu:

I wanted to say “Yay! Shorter code”, but I’m not 100% sure if it really is such a good thing.
If I can do
x = node.transform.pos.x
Then can I also do
x = node.transform.pos.x
x+=1 #??
and expect a change in position?

I don’t think, as far as I understood the change, there would be a set_x and get_x , with get_x you get a PyDouble (?), which is not related to the internal handle stored by the transform I believe.

wezu:

Someone might be also tempted to ‘enable’ shadow filtering by doing:
base.win.gsg.supports_shadow_filter=True
I think it might be confusing for some new users, especially if we have 3 ways of doing something x=spam.egg, x=spam.get_egg() and x=spam.getEgg(), but on the other side … Yay! Shorter code!

I guess the goal would be to have only way, like only supporting lower_case and properties.