-
-
Notifications
You must be signed in to change notification settings - Fork 21.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove duplicate displayed node update call #32908
Conversation
27882e4
to
7e93b68
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I did some tests with the code and it seems to work fine. I can also confirm that some things were needlessly called twice before this change. Though can't tell if it doesn't have some unexpected effects somewhere.
As it's not critical, let's merge it after 3.2 and cherry-pick if no regressions happen. |
@Nehluxhes Is this still desired? If so, it needs to be rebased on the latest master branch. |
7e93b68
to
c85d04a
Compare
@aaronfranke @akien-mga It is still desired and I just rebased on latest master. |
Thanks! |
Cherry-picked for 3.2.4. |
Each time a new node is selected in the scene tree dock, both
_node_selected()
and_selection_changed()
are called.They are then both calling
editor->push_item()
, resulting in potentially lots of duplicate calls downstream (eg a Gridmap node is loaded twice)This fixes this.
Ideally I think that _node_selected() and _selection_changed() should be merged, they are redundant.