-
Notifications
You must be signed in to change notification settings - Fork 165
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
xdg shell: Introduce reset_initial_configure_sent()
#1542
xdg shell: Introduce reset_initial_configure_sent()
#1542
Conversation
reset_initial_configure_sent()
reset_initial_configure_sent()
Another test client: wleird-unmap |
Hmm, why can't we do this automatically inside smithay, when we get a |
e97a2a6
to
14fd1da
Compare
Done, as long as the user uses Smithay's rendering abstractions this will now happen automatically. For any other case, the manual reset methods remain. |
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #1542 +/- ##
==========================================
+ Coverage 19.66% 19.69% +0.02%
==========================================
Files 169 169
Lines 27749 27851 +102
==========================================
+ Hits 5456 5484 +28
- Misses 22293 22367 +74
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
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!
14fd1da
to
85a60b5
Compare
As far as I can tell, the xdg initial configure dance has to be done every time a xdg surface remaps itself.
So this MR:
reset_initial_configure_sent
helper method for xdg_surface, that allows to resetinitial_configure_sent
/initial_decoration_configure_sent
tofalse
.Spec quote relating to this behavior: