-
-
Notifications
You must be signed in to change notification settings - Fork 18.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support removing TileMap
layer at negative index
#92015
base: master
Are you sure you want to change the base?
Support removing TileMap
layer at negative index
#92015
Conversation
The |
TileMap
layer at negative index
This is a follow-up to #54546, so it's probably fine for consistency. |
I don't mind much adding it for consistency. We will probably keep the TileMap node for a little while, and I don't think adding small tweaks matter much. My main goal in marking TileMap it as deprecated was to avoid contributors/users to implement/expect new features that would improve the TileMap node only, and that the focus will be on the TileMapLayer workflow instead. But like, if a new TileMap feature is small enough, restricted to the TileMap node, and does not need to be implemented in TileMapLayer too, I don't mind much. |
I didn't realise this. |
Co-authored-by: A Thousand Ships <96648715+AThousandShips@users.noreply.github.com>
Docs need description update here: Lines 324 to 329 in f4b047a
Example: Line 344 in f4b047a
Also you need to squash commits into 1. |
Added ability to
TileMap.remove_layer
using a negative index.