-
Notifications
You must be signed in to change notification settings - Fork 107
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
Sequence xdg-top-level and xdg-surface configure events correctly. #281
Conversation
@wmww I'm not convinced this is the best way fix this, do you have any thoughts on an alternative? |
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.
Good enough for now
bors r+
{} | ||
{ | ||
// TODO Make this readable!!! This "works" by exploiting the non-obvious side-effect | ||
// of causing a zxdg_surface_v6_send_configure() event to become pending. |
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.
Thanks for adding this comment
|
||
void mir::frontend::XdgSurfaceV6::set_next_commit_action(std::function<void()> action) | ||
{ | ||
next_commit_action = [this, action] |
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.
[non-blocking] perhaps next_commit_action
could be a vector so multiple lambdas can be added and executed with no danger of overwriting and not running an action.
Build succeeded |
qtwayland gets confused by receiving these event out of order. (Fixes #280)