You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This may be by design, but I didn't see it mentioned anywhere in the docs.
It appears that when inserting a Tile object it's anchor point differs from that of rectangles and ellipses. Please see the image below in which all objects are set to position 0, 0.
As you can see the anchor point for tile objects is the bottom left, whereas every other object type is top left.
The text was updated successfully, but these errors were encountered:
It is indeed an annoying inconsistency, and I'd like to fix it eventually but it'll require making the object origin configurable. There is another aspect to this which is that the origin of tile objects on isometric maps is the bottom-center rather than the bottom-left.
The documentation does mention it but it's a bit hidden, from the TMX Map Format page:
"When the object has a gid set, then it is represented by the image of the tile with that global ID. The image alignment currently depends on the map orientation. In orthogonal orientation it's aligned to the bottom-left while in isometric it's aligned to the bottom-center."
This may be by design, but I didn't see it mentioned anywhere in the docs.
It appears that when inserting a Tile object it's anchor point differs from that of rectangles and ellipses. Please see the image below in which all objects are set to position 0, 0.
As you can see the anchor point for tile objects is the bottom left, whereas every other object type is top left.
The text was updated successfully, but these errors were encountered: