Closed rolandoislas closed 8 years ago
Could you elaborate a bit more on what issue this fixes? Or what does this add?
Currently, when transforming a composite the origin is hard coded to (0,0). The boolean variable added to TransformComponent will now allow the settable origin to be used.
But if you have to set that default anyway for each component, why not set directly originX originY values instead?
For backwards compatibility. It's marked as a TODO. Really any implementation that would allow for values other than the hardcoded 0 would be nice.
So guys, why isn't this or #108 accepted and merged?
Backwards compatible. Defaults to false and uses (0,0) as origin.