Skip to content

Enable origin utilization in transform calculations#107

Closed
opencma wants to merge 1 commit intoUnderwaterApps:masterfrom
opencma:hotfix/transform-origin
Closed

Enable origin utilization in transform calculations#107
opencma wants to merge 1 commit intoUnderwaterApps:masterfrom
opencma:hotfix/transform-origin

Conversation

@opencma
Copy link

@opencma opencma commented Aug 28, 2016

Backwards compatible. Defaults to false and uses (0,0) as origin.

@azakhary
Copy link
Contributor

Could you elaborate a bit more on what issue this fixes? Or what does this add?

@opencma
Copy link
Author

opencma commented Aug 28, 2016

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.

@azakhary
Copy link
Contributor

But if you have to set that default anyway for each component, why not set directly originX originY values instead?

@opencma
Copy link
Author

opencma commented Aug 29, 2016

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.

@alexfacciorusso
Copy link

So guys, why isn't this or #108 accepted and merged?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants