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
Godot v4.3.beta3 - Windows 10.0.22631 - GLES3 (Compatibility) - NVIDIA GeForce GTX 1660 SUPER (NVIDIA; 32.0.15.5599) - Intel(R) Core(TM) i7-10700F CPU @ 2.90GHz (16 Threads)
Issue description
When you ctrl/cmd + left-click on a reference to a user-defined enum value in the Script Editor, it opens up a new tab with the documentation for the class that contains the user-defined enum, instead of taking you to the place in the code where that enum value is defined.
Furthermore, if the containing script does not have a class name, it opens up a blank documentation tab which can't be closed with the hotkey (but can still be closed via the right-click context menu).
While it is super cool that you can view a doc page for your own classes (I have no idea how else to trigger this behaviour but it's really cool!), this behaviour is inconsistent with the regular behaviour of ctrl/cmd + left-clicking on user-written types/values, which all take you to the place in the code that defines the item.
Steps to reproduce
Open up the attached project, and open up test_script.gd in the Script Editor.
Ctrl/Cmd + left-click on MyEnum.HELLO on line 6.
Notice that a new documentation tab opens up.
Erase the class name in the script, save, and repeat step 2.
Notice that a new blank documentation tab is created, and cannot be closed with the hotkey.
Tested versions
Reproducible in 4.3.beta3
System information
Godot v4.3.beta3 - Windows 10.0.22631 - GLES3 (Compatibility) - NVIDIA GeForce GTX 1660 SUPER (NVIDIA; 32.0.15.5599) - Intel(R) Core(TM) i7-10700F CPU @ 2.90GHz (16 Threads)
Issue description
When you ctrl/cmd + left-click on a reference to a user-defined enum value in the Script Editor, it opens up a new tab with the documentation for the class that contains the user-defined enum, instead of taking you to the place in the code where that enum value is defined.
Furthermore, if the containing script does not have a class name, it opens up a blank documentation tab which can't be closed with the hotkey (but can still be closed via the right-click context menu).
While it is super cool that you can view a doc page for your own classes (I have no idea how else to trigger this behaviour but it's really cool!), this behaviour is inconsistent with the regular behaviour of ctrl/cmd + left-clicking on user-written types/values, which all take you to the place in the code that defines the item.
Steps to reproduce
test_script.gd
in the Script Editor.MyEnum.HELLO
on line 6.Minimal reproduction project (MRP)
bug-report.zip
The text was updated successfully, but these errors were encountered: