-
Notifications
You must be signed in to change notification settings - Fork 63
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
[Bug]: Unable to make closed auto hidden docked page visible after config reloading #822
Comments
@dyurshevich Sorry for the delay, this seems to have slipped through the "cracks" |
No problem. Looks like the issue still exists. I've made some research myself and I believe the problem lies in KryptonAutoHiddenProxyPage. Can be tested much easier than I described initially with the following steps:
So, in short, looks like KryptonAutoHiddenProxyPage does not inherit Visibility property from its page when being deserialized from xml. The following code did the trick for me
|
thanks for the research and solution find. |
Hi @dyurshevich Please retry using |
…osed-auto-hidden-docked-page-visible-after-config-reloading * Resolves #822
Works fine, thank you. |
Describe the bug
Hi everyone.
I'm having an issue with making auto hidden docked page visible after loading dock config file. Visible property of the page becomes true, but page is still not shown. Worth to mention that config was saved with that page closed.
To Reproduce
The bug can be reproduced in demo app called Docking Persistence 2022.
Expected behavior
Page should appear
Desktop (please complete the following information):
Additional context
I did some research on that issue.
If we take a look at the call stack inside KryptonDockingManager.ShowAllPages(), we end up in KryptonNavigator.UpdateAllPagesVisible which in its turn loops through pages changing Visible property and calling ViewBuilder.PageVisibleStateChanged for every page.
In contrast, when we call KryptonDockingManager. ShowPage, page Visible property changes in KryptonDockingAutoHiddenGroup.PropogateAction and no ViewBuilder.PageVisibleStateChanged is called. Explicitly calling it fixes the issue.
The text was updated successfully, but these errors were encountered: