godotengine / godotengine/godot-visual-script
Easy VisualScriptPropertySelector Plugins
- Dominant language
- C++
- Stars
- 131
- Forks
- 25
- PR merge metrics
- No merged PRs in 30d
Description
### Describe the project you are working on
General Visual Script improvements
### Describe the problem or limitation you are having in your project
There is no easy way to try to improve VisualScriptPropertySelector. (It is like fuzzy finder or the autocomplete feature for VisualScript)
The current one is designed so beginners cant make mistakes. This leads to frustrations for advanced users and users coming from GdScript where that was never a consideration.
### Describe the feature / enhancement and how it helps to overcome the problem or limitation
Create an EditorVisualScriptPropertySelectorPlugin class including multiple subclasses for the different stages.
1. GuessDataOrSequence # It seems obvious but here also there are improvements possible.
2. GuessPropertyInfo # needs the VisualScript and current dragging port
For example to accurately guess that multiplying int and Vector3 results in Vector3. You need to know the output data of a and b input connections. (the math node itself changes to the last connected type)
3. GuessFilters # By default .vs provides functions from base classes while for example, InputEvent will definitely need all the functions of the inherited classes
4. CreateVSitem # To continue on InputEvent It will need to drop 2 nodes Typecast and the function.
### Describe how your proposal will work, with code, pseudo-code, mock-ups, and/or diagrams
No real design is done check feature steps
### If this enhancement will not be used often, can it be worked around with a few lines of script?
There is no workaround.
### Is there a reason why this should be core and not an add-on in the asset library?
It is to make workarounds and assets easier.
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.