mirror of
https://github.com/labwc/labwc.git
synced 2025-11-02 09:01:47 -05:00
ddc9047a67
Chases: 756ecf8ee9f1e75bc7b8297dc84f97c7d699174b backend/wayland: use request_state when toplevel is resized Chases: 3ef68a484243555b020200c6f95246d994932c3f backend/x11: use request_state when window is resized Ref: https://gitlab.freedesktop.org/wlroots/wlroots/-/merge_requests/2693 We now delay requested resolution changes by the backend until the next frame event which causes us to render the new content on the already enlarged buffer. Before this change, an empty (black) buffer would have been shown instead before the next frame event caused a new render of the actual contents. Keep commiting the new state and then scheduling a frame event would not help as due to the commit call it would still show an empty buffer in the meantime. Just modifying wlr_output->pending wouldn't work either because wlr_scene_output_commit() *completely* ignores it (and it will be removed in future wlroots commits). For this reason we move to wlr_scene_output_build_state() directly because it allows us to supply the current wlr_output->pending state and thus apply any resolution change in lockstep with new rendering. Result: No more flickering in the wayland backend and resizing is again smooth as butter. This prevents constant flicker while resizing when running nested via the wayland backend. For the X11 backend (can be tested via `WLR_BACKENDS=x11 labwc`), it is still rather janky but at least doesn't cause endless self- resizing anymore. |
||
|---|---|---|
| .. | ||
| array.h | ||
| border.h | ||
| buf.h | ||
| dir.h | ||
| fd_util.h | ||
| file-helpers.h | ||
| font.h | ||
| grab-file.h | ||
| graphic-helpers.h | ||
| list.h | ||
| macros.h | ||
| match.h | ||
| mem.h | ||
| nodename.h | ||
| parse-bool.h | ||
| scaled_font_buffer.h | ||
| scaled_scene_buffer.h | ||
| scene-helpers.h | ||
| spawn.h | ||
| string-helpers.h | ||