-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Improvements to swaynag rendering #8437
Open
mstoeckl
wants to merge
3
commits into
swaywm:master
Choose a base branch
from
mstoeckl:swaynag-redraw
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from 1 commit
Commits
Show all changes
3 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
In the resize case, shouldn't we wait for the compositor's configure event as well?
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.
I believe we do not need to and the cost is greater than the benefit.
I assume the layer shell configure event is fundamentally a hint, similar to xdg-shell. On rereading, I find I can't exactly parse the grammar of the protocol text for the configure event, but it seems to point in the right direction.
At any rate, there is no "dimension_mismatch" error for ignoring the size as there is for ext-session-lock.
Consequently, if a layer shell client wants to use a specific size, it can just send a buffer (and, optionally, a set_size request), and acknowledge and disregard any following configure events. (The risk is that the compositor might clip the surface if it the client's provided size is infeasible.) In practice, sway appears to just reply with a configure event with height matching set_size, so there is no disagreement.
In fact, the documentation for the layer shell
set_size
request saysso it looks like the compositor should always match the suggested height from set_size in its next configure event, unless there is some scale change, output layout change, or other unusual event (in which case the width might change and the compositor send a new configure event.)
Therefore: waiting for the compositor's configure event introduces an extra roundtrip of delay before a new buffer can be committed, and its benefit (the client not committing a wrong-sized buffer) only occurs in the case where the configure width depends on the set_size height.
(Waiting also brings a theoretical risk of livelock, where the client could never commit a new buffer if the compositor never gives it the height it asked for -- but this should not happen per
set_size
documentation.)Misc note: swaynag's current rendering code seems to be a weird mix of attempting to adapt to the recommended height value from the configure (see comparisons with swaynag->height in render_message, render_button) and ignoring it (render_detailed).