linux: wayland: Fix order of wayland messages #387
Merged
Conversation
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
Draft
Bind to the globals in the correct order and make sure Wayland objects are created before they are used. Instead of doing a roundtrip each time when we send a message to the server, the queue gets flushed to improve the performance
pentamassiv
force-pushed
the
wayland_bind_globals
branch
from
381917f to
a13c896
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Bind to the globals in the correct order and make sure Wayland objects are created before they are used. Sending messages to objects before they were created caused
labwcto crash.Instead of doing a roundtrip each time when we send a message to the server, the queue gets flushed to improve the performance,