Add math operators to Visual Shader node names for easier and simpler searching

[alfredbaudisch]

This change makes it easy, in the "Create Shader Node" dialog, to search for VS nodes by just typing the operator. For example, instead of typing "multiply", you can just type "*" and multiply nodes will be listed.

Searching by name still works as you can see in the example video.

This feature is inspired by Unreal Engine node graph editor's UX.

Implements and closes godotengine/godot-proposals#5663

godot-search-operator.mp4

[QbieShay]

@Chaosus does this break compatibility?

[alfredbaudisch]

@Chaosus does this break compatibility?

@QbieShay what does it affect in this case? Because the original Node names are still preserved in the graph, the names with operators appear only in the "Create Shader Node" dialog and in the search.

[alfredbaudisch]

@Chaosus does this break compatibility?

@QbieShay I figured it out here. From what I tested, it doesn't break compat:

• I created a project and a Visual Shader with Godot4-beta3.
• I then opened the project with Godot with this change and it works.
• Then vice-versa.

[sub_resource type="VisualShaderNodeFloatOp" id="VisualShaderNodeFloatOp_j0vv5"]
operator = 2

The reason is that the Nodes in the graph do not keep the names with the operators, the operators appear only in the add dialog, i.e. add_options.push_back, where AddOption("Equal (==)" is just the title of the dialog option.

Ex:

add_options.push_back(AddOption("Equal (==)", "Conditional/Functions", "VisualShaderNodeCompare", vformat(compare_func_desc, TTR("Equal (==)")), { VisualShaderNodeCompare::FUNC_EQUAL }, VisualShaderNode::PORT_TYPE_BOOLEAN));

[Chaosus]

does this break compatibility?

Nah, it's just a some sort of small UI enhancement. Make sense to me.

[clayjohn]

Looks great, thanks!

[Calinou]

Out of curiosity, can this PR be remade for 3.x as well?

[alfredbaudisch]

Out of curiosity, can this PR be remade for 3.x as well?

I'm checking it out.