Godot: Going back in the Inspector while editing a GridMap node makes it and the previous node selected

[YeldhamDev]

Godot version:
2db4942

Issue description:
Basically this:

[vazzup]

Hi, I'd like to help. Could you specify steps to recreate the bug?

[YeldhamDev]

@vazzup Basically what's said in the title, select a GridMap node, go back in the inspector, using these:

And both the GridMap and the previous node will be selected.

[vazzup]

Ok, thanks. Will look into it

[BornStellarMakesEternalLasting]

I can confirm this happens in 3.0.2 and 3.0.6. The inspector arrows don't seem to disselect what is in the history. I've also seen that this works with more nodes than just the gridmap node.

[vazzup]

Yes, it is also a bug in the master branch. Also, if there are multiple previous nodes, all of them get selected.

[vazzup]

I'm looking at the editor_node.cpp file and I think the change will be around line no. 1476 in the _edit_current function.

[vazzup]

Hi, after digging deep, I'm a bit stuck with this bug. I think the bug may be from the EditorInspector::update_tree function, but I can't say for sure. Can someone else please point me in the right direction?

[avril-gh]

I've also seen that this works with more nodes than just the gridmap node.

theres also strange behavior while debugging remote tree (which is running on android device),
When one select a node (in debugger) , other nodes will select itself randomly, and theres no way to stop it, thus no way to use this feature to debug / change properties in inspector at runtime, ect.
Its not easy to reproduce it on simple project with fiew nodes created in editor,
but it begin to appear in projects with higher count of nodes created at runtime.

Just mentioning it here, since it sounds similar, ...but perhaps i should make a new issue for this.

[DeuxAlpha]

Hi! I'm able to reproduce the bug, but it doesn't seem to be related to GridMaps only. In my case, any node will cause this issue. It doesn't seem to influence functionality, however, since the inspector displays the correct Node and its properties. The only issue is that several nodes _look_ highlighted. Additionally, the further you go back in history, the more Nodes get highlighted (once again, not influencing functionality, but aesthetics only).

EDIT:
Another thing I just noticed was that the bug only seems to occur on Spatial Nodes, but not on any other type of Node. For example, if I traverse the history between spatial nodes, the bug appears, but if I move to another type of node, the bug does not occur and/or fixes itself (i.e. only the actually selected Node is highlighted). If I move to a spatial Node from a different kind of node, both the different one and the spatial Node stay selected (and any other spatial Nodes the further backwards I go).

FYI, the behavior stays the same no matter whether I move forward or backward in history.

[KoBeWi]

Still valid in 4e0f31a
As mentioned above, this applies not only to GridMap, but also mixed-type nodes, e.g. when you select Node2D then Spatial, then go back and then forward (going back doesn't seem to trigger it), both get selected. Might be somehow related to #36291