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.xThen can I also do
x = node.transform.pos.x
x+=1 #??and expect a change in position?
Someone might be also tempted to ‘enable’ shadow filtering by doing:
base.win.gsg.supports_shadow_filter=TrueI 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!
As for the camelCase… I kind of like them, but I’m dyslectic and sometimes I can mistake a “.” for a “_” or vice versa, with camelCase it’s less likely to make a mistake like that, but I also keep writing “elf” instead of “self” so I’ll always find some way of making errors. I won’t cry (much) if cameCase goes away 