-
-
Notifications
You must be signed in to change notification settings - Fork 21.4k
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
GDScript 2.0: @export_category
interferes with the property inspector tooltip
#64432
Comments
@export_category
interferes with the property inspector tooltip
I can't reproduce the bug in 4.2-dev5, while it's reproducible up to 4.2-dev4. I don't see right away which change would have solved it in https://godotengine.github.io/godot-interactive-changelog/#4.2-dev5, maybe @dalexeev has an idea? |
It also depends on placement of
Though if it would be placed on the first place, then it won't work :
|
@TechnoLukas See #88318. For the future, feel free to open a new issue instead of commenting on a closed old one. |
Godot version
v4.0.alpha.custom_build [f2a6168]
System information
Linux
Issue description
Properties can be documented by giving them a description with
##
comments. That description is then showed as a tooltip in the inspector, like this.However, any properties following an
@export_category
annotation will only have a "no description" tooltip.This bug actually predates
@export_category
and also occurs when usingPROPERTY_USAGE_CATEGORY
directly in_get_property_list()
.The problem is that
EditorInspector::update_tree()
assumes that any property withPROPERTY_USAGE_CATEGORY
either has aname
that is a class name or ahint_string
that is a path to a script. And it uses that class/path to look up the description of subsequent properties.One possible fix is to simply add the required hint string to
@export_category
. I've verified that this works.One downside to that is that the tooltip of the category itself will be the description of the script ("This is a description of the script" in the screenshots above).
I guess the alternative is to change
EditorInspector::update_tree()
which is a 670 line hairy monster.Steps to reproduce
See screenshots above.
Minimal reproduction project
No response
The text was updated successfully, but these errors were encountered: