mirror of
https://github.com/brl/mutter.git
synced 2024-11-21 15:40:41 -05:00
e8052f169b
During animation or other things that cause multiple frames in a row being painted, we might skip recording frames if the max framerate is reached. Doing so means we might end up skipping the last frame in a series, ending with the last frame we sent was not the last one, making things appear to get stuck sometimes. Handle this by creating a timeout if we ever throttle, and at the time the timeout callback is triggered, make sure we eventually send an up to date frame. This is handle differently depending on the source type. A monitor source type reports 1x1 pixel damage on each view its monitor overlaps, while a window source type simply records a frame from the surface directly, except without recording a timestamp, so that timestamps always refer to when damage actually happened. https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1351 |
||
|---|---|---|
| .. | ||
| backends | ||
| compositor | ||
| core | ||
| meta | ||
| tests | ||
| ui | ||
| wayland | ||
| x11 | ||
| libmutter.pc.in | ||
| meson.build | ||
| meta-marshal.list | ||
| org.freedesktop.login1.xml | ||
| org.gnome.Mutter.DisplayConfig.xml | ||
| org.gnome.Mutter.IdleMonitor.xml | ||
| org.gnome.Mutter.RemoteDesktop.xml | ||
| org.gnome.Mutter.ScreenCast.xml | ||