-
-
Notifications
You must be signed in to change notification settings - Fork 21.8k
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
Fix broken bottom panel switching #72420
Fix broken bottom panel switching #72420
Conversation
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.
Approving, but this might be a temporary solution, or at least it requires further fixes.
Ghost editors seem to have existed before this PR... |
6adf857
to
8668c06
Compare
8668c06
to
fc22583
Compare
This fixes the switching bug, but I found a side effect in the EditorPlugin which may spam switching in the bottom panel, may cause problems with the bottom panel closing unwillingly. The ones I have encountered so far are SpriteFramesEditor and ThemeEditor, but they may need to be addressed individually. Also, the ghost editor has existed prior to this PR, but that may need to be fixed as well. |
Thanks! |
Note: The issue with the theme editor seemed to be a different problem #72271 |
This seems to have caused another issue - I'm using a custom editor plugin that updates whenever a node is selected. However, after beta 17, the This means I have to select a node that causes my custom dock to hide, then select another node that makes it appear again to get it to update at all. I don't see exactly how this could have been caused by this fix, but I don't see any other PRs that changed EditorPlugin since beta 16 (where everything worked as expected) |
The cause of the crash is simple recursion. Switching events bound to buttons on the bottom panel were being called recursively by inspector updates.
The inability to transition to the animation tab is due to the inspector update, which can be resolved by the restriction that bottom tab switching is allowed only once in the same frame. This means that the pending update method of #68498 cannot be used.