[Visual Debugger] Should positions be shown instead of origins? #3395
Replies: 2 comments 5 replies
-
I'm not sure I understand the ask/improvement here. As far as I know, everything (other than hitboxes or sprites) uses the origin point as the logical source of truth for location. When you position an object by events, it doesn't use AABB, it uses the origin point. Flipping happens on center, but rotation uses origin on every test I can do in the web demo. Whatsmore, origin point being a source of truth is important as it allows users to move the sprite rendering position without adding more empty space to the art asset by moving the point in yhe points editor. I would look for someone like @4ian or one of the crew to chime in more incase I'm totally off base and missing something. |
Beta Was this translation helpful? Give feedback.
-
I just learned what you talk about in this post; Object.X() and Object.Y() don't move when the object is rotated. This is highly unexpected. I think we should add new points called Object.OriginX() and Object.OriginY() that do move when the object is rotated. What do you think? |
Beta Was this translation helpful? Give feedback.
-
The visual debugger shows the origin point. I think that this point doesn't have any meaning for the events.
The events use the position of the object. This is not the same thing as the origin as the position doesn't change when the object rotate.
This short video shows an object rotating with the position instead of the origin:
https://user-images.githubusercontent.com/2611977/147014245-d3cffe37-e27f-43e3-8d4a-6892613fa429.mp4
I think that showing the position is more useful and allows to better understand how
X()
andY()
work.Beta Was this translation helpful? Give feedback.
All reactions