Add surface_enter/surface_leave methods to CompositorHandler
#451
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
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.
While the
outputs()method onSurfaceDataallows an app to retrieve the current outputs of a surface, it's not currently possible to easily detect changes to this value.This pull-request adds the
surface_enter/surface_leavemethods to theCompositorHandlertrait. These methods correspond to thewl_surface::enter/wl_surface::leaveevents and should make it easier for client apps to detect changes to a surface's outputs.Note
See https://github.com/vially/flutter-rs/commit/03ff77836c12e0092b6a46f7445013f9a48c1035 for a more realistic use-case of these methods.