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
Creating a plugin/tool that implements a DualGrid TileMap system for 16 autotiles
Describe the problem or limitation you are having in your project
We have to resort to using _process as well as keeping a cached copy of get_used_cells() in order to figure out when a cell has been added or removed. Also the "changed" signal does not get emitted when adding or removing cells, I'm not sure if that is intentional or a bug.
Describe the feature / enhancement and how it helps to overcome the problem or limitation
It would be a relief for there to be a signal that gets emitted when cells have been modified along with the cell coordinate so that cell modifications can be easily and distinctively be processed without having to do runtime comparisons of cached cell data in order to figure out what has changed.
Describe how your proposal will work, with code, pseudo-code, mock-ups, and/or diagrams
Add a signal to TileMapLayer class and emit the signal at the end of the set_cell function.
If this enhancement will not be used often, can it be worked around with a few lines of script?
I suspect this will not incur much of any penalty at all for those who don't use it.
Is there a reason why this should be core and not an add-on in the asset library?
Adding add-ons is cumbersome and this a feature that any potential add-ons working with TileMapLayer's could need or at least it would make life easier for them with just a couple lines of code.
The text was updated successfully, but these errors were encountered:
Well, actually, quick correction. The signal has not been implemented, but virtual method has. So I'm swiftly reopening again after this lapse in judgement.
If you believe this proposal is no longer necessary, feel free to close it.
Describe the project you are working on
Creating a plugin/tool that implements a DualGrid TileMap system for 16 autotiles
Describe the problem or limitation you are having in your project
We have to resort to using
_process
as well as keeping a cached copy of get_used_cells() in order to figure out when a cell has been added or removed. Also the "changed" signal does not get emitted when adding or removing cells, I'm not sure if that is intentional or a bug.Describe the feature / enhancement and how it helps to overcome the problem or limitation
It would be a relief for there to be a signal that gets emitted when cells have been modified along with the cell coordinate so that cell modifications can be easily and distinctively be processed without having to do runtime comparisons of cached cell data in order to figure out what has changed.
Describe how your proposal will work, with code, pseudo-code, mock-ups, and/or diagrams
Add a signal to TileMapLayer class and emit the signal at the end of the set_cell function.
I have created a pull request 97896
If this enhancement will not be used often, can it be worked around with a few lines of script?
I suspect this will not incur much of any penalty at all for those who don't use it.
Is there a reason why this should be core and not an add-on in the asset library?
Adding add-ons is cumbersome and this a feature that any potential add-ons working with TileMapLayer's could need or at least it would make life easier for them with just a couple lines of code.
The text was updated successfully, but these errors were encountered: