Skip to content
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

Handle session lock surfaces in visible_outputs_for_surface #224

Merged
merged 2 commits into from
Nov 15, 2023

Conversation

ids1024
Copy link
Member

@ids1024 ids1024 commented Nov 14, 2023

Fixes issue with re-draw not being queued on initial surface commit until cursor is moved.

Fixes issue with re-draw not being queued on initial surface commit
until cursor is moved.
@ids1024
Copy link
Member Author

ids1024 commented Nov 14, 2023

Added a commit to schedule a renderer when the session lock is created or destroyed, which also improves behavior in certain cases.


for output in self.common.shell.outputs() {
self.backend
.schedule_render(&self.common.event_loop_handle, &output, None);
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Seeing None here for the screencopy-sessions reminds me... how do we want to handle screencopy, if a session-lock is active?

I don't think we want to capture the lock-screen (do we??), so perhaps we should suspend them while the lock is active and never return a new frame?

Copy link
Member

@Drakulix Drakulix left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No need to block this on the open discussion though, the changes seem very sensible.

@Drakulix Drakulix merged commit b33c1dc into master_jammy Nov 15, 2023
4 checks passed
@jackpot51 jackpot51 deleted the session-lock-visible_jammy branch November 15, 2023 14:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants