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
Describe the project you are working on:
gdscript plugins
Describe the problem or limitation you are having in your project:
When there are many methods and properties in a script, then there is a desire to have flexible settings for displaying these properties and methods in the Code Editor autocomplete window (popup).
For example I really miss
a smarter methods sorting (for example, taking into account the most frequently selected/used methods, etc.),
or even adding some custom results.
I tried to solve this using plugins, but it seems like now it is impossible to get the code autocompletion popup window or do anything with it.
Describe the feature / enhancement and how it helps to overcome the problem or limitation:
The solution could be to open access to the API for Autocomplete methods and, in general, in the ability to add a custom logic to Autocomplete using plugins.
This would allow flexible customization of autocomplete to fit ones needs.
Describe how your proposal will work, with code, pseudocode, mockups, and/or diagrams:
Ability to get a list of autocomplete results and filter them, sort and add new results.
Using a plugin, one could get the autocomplete class (say via get_editor_interface().get_script_editor().get_completion() and then use the methods, properties and signals of this class to modify the autocomplete results.
Or to create and use custom Autocompletions using Autocomplete plugins, for example by analogy with the Inspector plugins.
The ability to change the appearance of the autocomplete window would also be convenient (here's an example where tabs are added to the autocomplete window godotengine/godot#38449 (comment))
If this enhancement will not be used often, can it be worked around with a few lines of script?:
No, there's no way to work around it
Is there a reason why this should be core and not an add-on in the asset library?:
I think this couldn't be implemented as an add-on since there is no API for it
The text was updated successfully, but these errors were encountered:
Describe the project you are working on:
gdscript plugins
Describe the problem or limitation you are having in your project:
When there are many methods and properties in a script, then there is a desire to have flexible settings for displaying these properties and methods in the Code Editor autocomplete window (popup).
For example I really miss
I tried to solve this using plugins, but it seems like now it is impossible to get the code autocompletion popup window or do anything with it.
Describe the feature / enhancement and how it helps to overcome the problem or limitation:
The solution could be to open access to the API for Autocomplete methods and, in general, in the ability to add a custom logic to Autocomplete using plugins.
This would allow flexible customization of autocomplete to fit ones needs.
Describe how your proposal will work, with code, pseudocode, mockups, and/or diagrams:
Ability to get a list of autocomplete results and filter them, sort and add new results.
Using a plugin, one could get the autocomplete class (say via
get_editor_interface().get_script_editor().get_completion()
and then use the methods, properties and signals of this class to modify the autocomplete results.Or to create and use custom Autocompletions using Autocomplete plugins, for example by analogy with the Inspector plugins.
The ability to change the appearance of the autocomplete window would also be convenient (here's an example where tabs are added to the autocomplete window godotengine/godot#38449 (comment))
If this enhancement will not be used often, can it be worked around with a few lines of script?:
No, there's no way to work around it
Is there a reason why this should be core and not an add-on in the asset library?:
I think this couldn't be implemented as an add-on since there is no API for it
The text was updated successfully, but these errors were encountered: