We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
My application performs an automatic layout restoration during launch. The call is done from the page constructor.
To produce the issue, we perform the following:
After some testing it seems this is caused by a small piece of the restoration logic being run in the wrong thread.
Specifically, the Show call is being done via Dispatcher.BeginInvoke() while WindowState property is set outside of this.
I have made changes to correct the behavior by moving the setting of WindowState to within the same scope as Show(), and will create a pull request.
The text was updated successfully, but these errors were encountered:
Pull Request #490 has been created to address this issue. I am unsure how to link this issue to the pull request.
Sorry, something went wrong.
No branches or pull requests
My application performs an automatic layout restoration during launch.
The call is done from the page constructor.
To produce the issue, we perform the following:
When this is done, the LayoutAnchorableFloatingWindow is not restored to maximized state.
After some testing it seems this is caused by a small piece of the restoration logic being run in the wrong thread.
Specifically, the Show call is being done via Dispatcher.BeginInvoke() while WindowState property is set outside of this.
I have made changes to correct the behavior by moving the setting of WindowState to within the same scope as Show(), and will create a pull request.
The text was updated successfully, but these errors were encountered: