Allow to select multiple remote nodes at runtime

[YeldhamDev]

Closes #93628.

Screencast_20241125_111648.webm

Features Implemented

• Multi selection of multiple nodes, even if from different types. The properties shown in the inspector will be the ones shared by all the ones selected, like how MultiNodeEdit works.
• Region selection for Node2D/Control and Node3D nodes.
• Additive selection: holding Shift will add/remove items to the selection group instead of overriding it.

Sponsored By: 🐺 Lone Wolf Technology / 🍀 W4 Games.

[YeldhamDev]

I want some feedback on how to handle limiting selection of too many nodes, because that carries the risk of encoding of the data failing and no selection occurring.

• What the default limit should be? 10-ish or so?
• Should it be a hard limit, not allowing to select further nodes? Or a soft one, only printing a warning when the limit is exceeded?

[KoBeWi]

Maybe hard limit with warning?
How many nodes can be selected before it breaks?

[YeldhamDev]

@KoBeWi Missed your message, sorry.

It depends on the data size of the objects. On my end for example, selecting more than 30 Button nodes starts to break things.

[KoBeWi]

So limit it to 20-25, if someone tries to select more nodes pop a warning toaster. The limit can be configurable in editor settings. Personally I rarely select more than 5 nodes; most often it's to move them in the scene, which is not something you can do in Remote tree.

[YeldhamDev]

The selection limit has been implemented.

[KoBeWi]

You could instead replace it with editor layout. It's global for editor.
The project metadata are per-project, not very useful for Game tab.

[YeldhamDev]

I would actually disagree. Different projects sometimes require different workflows, so making those be kept in a per-project basis makes sense.

[Calinou]

Tested locally, it works as expected. It works in mixed 2D-3D scenarios too:

select_multi.mp4

PS: The orange selection gizmos in 3D still seem to receive shadows (unlike in the editor where they render as expected). I thought this was fixed at some point.

[YeldhamDev]

@Calinou The rendering of those use the same flags as the ones in the editor, so I dunno what could be causing it.

[YeldhamDev]

Alright, EditorDebuggerRemoteObject and EditorDebuggerMultiRemoteObject have been merged into EditorDebuggerRemoteObjects which handles both single and multi selections.

[YeldhamDev]

@KoBeWi

Properties of remote nodes can't be filtered. The LineEdit immediately loses edit focus.

Try again, please.

[AeioMuch]

When you select a node the first time, it shows correctly as the one edited at the top of the inspector, but selecting another node does not update it, the first one still shows.

Also the editor selection history does not work properly, selecting another node update the previous entry instead of adding a new one.

godot.windows.editor.x86_64_jneUqvm8CL.mp4

[YeldhamDev]

@AeioMuch Should be fixed now.

[AeioMuch]

@AeioMuch Should be fixed now.

It works fine now 👍, but there's is still a small issue remaining : while using the drop down menu of recently edited object will properly reselect the correct node(s) in the remote scene tree, using the backward and forward arrows will not reselect them, only update the inspector.

[YeldhamDev]

@AeioMuch Try again.

[AeioMuch]

@AeioMuch Try again.

Fixed! Well done 😀