fix workspace docking bug #14
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 #13
When a workspace switches from Stack Mode to Tab Mode, it will rely on the components rootParentChangeListener to undock and redock the
dockedComponentin its new location (TabPane in this case). ThiscallOnDockin the listener is not doneinDynamicComponentMode, meaning any workspace buttons added in the componentsonDockfunction would not be marked for removal upon anonUndockcall.This fix briefly removes the listener of the component for its workspace dock call in this single instance.
Line 296ensures the component will be dockedinDynamicComponentModeas expected.