-
Notifications
You must be signed in to change notification settings - Fork 325
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
Floating Window Group does not hide correctly #28
Comments
#28 Plus additional tool windows 1-3 for testing with tool windows
A possible solution is documented in FloatingWindowGroup branch. This commit changes the:
This code makes the Tool Window re-appear in the MainWindow when the user tries to unhide it after hidding the FloatingWIndow. |
I've tested a little bit with floating windows and found a workflow that was not working OK as a result of the first fix candidate:
The cause of this new issue seems to be the So, just for clarities sake - the current idea on the fix is this change:
This code makes the Tool Window re-appear in the MainWindow when the user tries to unhide it after hidding the FloatingWIndow. |
Issue
A Floating Window (Group with at least 2 tool windows) does not hide correctly.
The framework hides only the toolwindows but leaves floating window empty.
There is a NullReference Exception + Crash when user tries to drag the flowting tool window.
Steps to verify (using the MLib_Test client)
Drag 2 tool windows (LayoutAnchorable) into one floating window
![Crash CloseFloatingWindowGroup CloseButton Drag](https://user-images.githubusercontent.com/2129700/57311070-3d533700-70eb-11e9-9f1e-7d01708aad3e.png)
Close MLib_Test Application to Save the Layout
Restart MLib_Test Application to Reload the Layout
Click Hide (button) of the floating window
![Crash CloseFloatingWindowGroup CloseButton Drag_1](https://user-images.githubusercontent.com/2129700/57311145-61af1380-70eb-11e9-84b7-7140749fec81.png)
Bug
AvalonDock.Layout.txt
Crash is reproducable with this layout but somehow not with above steps anymore(?):
The text was updated successfully, but these errors were encountered: