-
-
Notifications
You must be signed in to change notification settings - Fork 220
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
send frame callbacks for active screencast windows #642
base: main
Are you sure you want to change the base?
Conversation
75af433
to
26f5c46
Compare
26f5c46
to
37dadf9
Compare
37dadf9
to
2c56c07
Compare
|
||
// FIXME: when a window is hidden, it should probably still receive frame callbacks | ||
// and get rendered for screen cast. This is currently | ||
// unimplemented, but happens to work by chance, since output | ||
// redrawing is more eager than it should be. |
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.
So, this comment should not be removed, it still stands. What this PR does is sends frame callbacks to off-screen windows, which makes them commit a new buffer. Which currently makes niri always redraw the output and hence render a new frame for a screencast. However, ideally niri shouldn't redraw the output if the window that committed a new buffer is fully off-screen. I will at some point add that optimization, which will once again stop off-screen windows from rendering for screencasts (or receiving frame callbacks from this PR for that matter), until this is fixed in a different way.
output, | ||
frame_callback_time, | ||
FRAME_CALLBACK_THROTTLE, | ||
|_, _| Some(output.clone()), |
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 think instead of being a separate function, this cast check should be integrated into send_frame_callbacks()
where it should be part of the if current_primary_output.as_ref() != Some(output)
check. The stuff in send_frame_callbacks()
does throttling to at most one frame callback per output refresh; without it windows will busy-loop frame callbacks (especially so off-screen windows, which is the primary case here).
Fixes #539. cc @yuu-fur who originally brought this issue to my attention, he might find this interesting.
I don't really know what i'm doing here. Frame callbacks are confusing. But this looks entirely reasonable to my eyes, and i've tested it on my own system and it seems to work.