-
-
Notifications
You must be signed in to change notification settings - Fork 97
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
Add property context menu to Inspector #3098
Comments
See also #1504. |
I see no harm and should be easy to implement. Feel free to open a PR, I think. For your problem though a drag'n'drop support would be even more useful, IMO. As in, dragging from the property label onto a script should insert the property path. |
Partially implemented by godotengine/godot#39404. We have a context menu now with copy/pase, but it needs an Open In Help option to close this proposal I guess. |
I opened a PR to add an "Open Documentation" button, so the only part of this proposal left is the "Reset to Default" button. I didn't add it to the PR because don't see much of a use for it, but someone else can open a PR for that if they want to. But if the reset button isn't really needed, then this proposal can be closed after the PR is merged. |
Describe the project you are working on
A game that uses
AnimationTree
.Describe the problem or limitation you are having in your project
If you want to set parameter of some
AnimationTree
parameters, one have to write:The property path is quite long and no auto-complete available. But it's there in the property's tooltip :(
Describe the feature / enhancement and how it helps to overcome the problem or limitation
Add a context menu for properties in the Inspector. Put options like "Copy Value", "Copy Path", and "Open in Help" in it.
Describe how your proposal will work, with code, pseudo-code, mock-ups, and/or diagrams
Right-clicking a property pops up a context menu like this:
If this enhancement will not be used often, can it be worked around with a few lines of script?
Possible, but not a few lines I think.
Is there a reason why this should be core and not an add-on in the asset library?
It's a bit strange to download a plugin to solve the UX problem.
The text was updated successfully, but these errors were encountered: