-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
Don't auto-dismiss the warning dialog on launch #15273
Don't auto-dismiss the warning dialog on launch #15273
Conversation
This comment has been minimized.
This comment has been minimized.
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.
This seems like us working around implicit magic. Is there no way to suppress the WM_MOVE?
Didn't seem like it. I might be able to filter based off if the old window rect and the new one are the same, but that might not work for the initial show |
// Don't set our state to Initialized until after the call to ShowWindow. | ||
// When we call ShowWindow, the OS will also send us a WM_MOVE, which we'll | ||
// then use to try and dismiss an open dialog. This creates the unintended | ||
// side effect of immediately dismissing the initial warning dialog, if | ||
// there were settings load warnings. | ||
// | ||
// In AppHost::_WindowMoved, we'll make sure we're at least initialized | ||
// before dismissing open dialogs. |
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.
BODGY?
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.
Apparently,
ShowWindow
also sends aWM_MOVE
, which we then turn around and use to dismiss open dialogs.Closes #15170
Regressed in #13811