Fix wrong inspected node after drag&drop #94105
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #93935
The problem was that after dropping a node the inspector is updated automagically due to EditorSelection change, and the change does not happen when nodes are simply moved in parent instead of reparented (because they don't leave scene tree).
The fix relies on the fact that the editing history holds the old object after hovering, which technically can be considered a bug (as I noted in #91265 (review)), but right now it's the simplest solution.