From 30f2ec8185788b6e9a260d77077a2ef2ebed53b2 Mon Sep 17 00:00:00 2001 From: ManoloFLTK <41016272+ManoloFLTK@users.noreply.github.com> Date: Thu, 28 Dec 2023 11:28:47 +0100 Subject: Fix for bug in Mutter Wayland compositor (#878) - cont'd Add more tests to do additional operations under stricter conditions --- documentation/src/wayland.dox | 5 +++++ 1 file changed, 5 insertions(+) (limited to 'documentation/src') diff --git a/documentation/src/wayland.dox b/documentation/src/wayland.dox index 5a16311d6..d1ba01e00 100644 --- a/documentation/src/wayland.dox +++ b/documentation/src/wayland.dox @@ -636,6 +636,10 @@ is off and Wayland sends a final resize command which is not skipped. Overall, t ensures the client program resizes its window as frequently as it can without falling behind resize commands sent by the compositor. +To account for a bug in Mutter (issue #878), the \c window->buffer->cb object is +not created when a toplevel window is being resized and is entirely covered by +one subwindow. +

Progressive window drawing

FLTK supports progressive drawing when an app calls function Fl_Window::make_current() at any time and then calls the FLTK drawing API. This is made possible @@ -1280,6 +1284,7 @@ struct wld_window { int floating_width; // helps restoring size after un-maximizing int floating_height; int state; // indicates whether window is fullscreen, maximized. Used otherwise for POPUPs + bool covered; // specially for Mutter and issue #878 } -- cgit v1.2.3