[Wayland-bugs] [Bug 699587] wayland: ensure the window is not maximised while being moved

gtk+ (bugzilla.gnome.org) bugzilla at gnome.org
Mon May 6 09:35:34 PDT 2013


https://bugzilla.gnome.org/show_bug.cgi?id=699587
  gtk+ | wayland | unspecified

Kristian Høgsberg <krh> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |krh at bitplanet.net

--- Comment #4 from Kristian Høgsberg <krh at bitplanet.net> 2013-05-06 16:35:29 UTC ---
I think this is one of those things that need compositor side support. 
Typically you want a little but of motion threshold before you unmaximize and
move the window, which has to be done by the compositor.  The application sends
a move request as usual and the compositor will check motion against the
threshold.  Once the threshold is exceeded, the compositor sends an unaximized
event, and when the application responds with new buffer, the compositor can
start moving the window.

What's missing here is the request_unmaximize event that allows the compositor
to request the application to unmaximize.  The application responds by
unmaximizeing and sending a new buffer (renderered with decorations and shadow)
at which point the compositor can start moving the surface.

-- 
Configure bugmail: https://bugzilla.gnome.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.


More information about the Wayland-bugs mailing list