Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Assets/Instance positions aren't locked to tiles #2

Open
nickavv opened this issue Jun 27, 2020 · 0 comments
Open

Assets/Instance positions aren't locked to tiles #2

nickavv opened this issue Jun 27, 2020 · 0 comments
Labels
enhancement New feature or request

Comments

@nickavv
Copy link
Member

nickavv commented Jun 27, 2020

If the room is resized in an increment that does not match the tile size assets/instances can come "detached" from where they appear like they should be relative to the tile layers.

This is because assets/instances are moved the exact amount of pixels needed to match the new room size and anchoring, whereas tiles by necessity are moved on a perfect tile grid. So if you added 8 pixels to the room's width, for instance, with right-hand anchoring, all assets/instances would be moved over 8 pixels while the tileset may get a new column of tiles added which ends up visibly moving the tiles over by 16 pixels.

Technically this is correct but it isn't a good user experience. Currently the "Round up to nearest tile size?" option mitigates this, but finding a better way to handle it or a more seamless user experience would be great.

@nickavv nickavv added the enhancement New feature or request label Jun 27, 2020
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant