-
-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Scripting API - Signal for when the active layer was changed #3246
Comments
Already available but undocumented, this is covered by the signals
But I agree this would be a rather more convenient approach! |
I love the idea of being able to specify layers for which the tool should be active (or perhaps inactive?). However, I wonder if it might perhaps be better to specify a single property like It would be cool to have an additional property that decides whether to activate the tool when any of the selected layers are valid vs requiring all selected layers to be valid. Or I guess there can be one default behaviour, and if someone wants it different, they can override it in their script. Perhaps in the future, if Tileset tools are ever added, this could be expanded with |
Maybe you or @BlaXun would like to open a separate issue for this? |
On it. |
I think it would be helpful if there was a signal emitted when the active layer was changed. That way we could enable/disable tools. For example I got tools that don't create tiles but objects. I'd like those tools to only be active when an object layer was chosen.
Another way to get this done would be to have a new property on tools such as "allowForObjectLayers", "allowForTileLayers". Would make it even easier for extension developers I assume
The text was updated successfully, but these errors were encountered: