all repos — fluxbox @ 6dca40aae6e0b0d923cc5eb7d18bb53c0a42482e

custom fork of the fluxbox windowmanager 

Fix regression in rendering the Window-Motion-Outline

Commit 79fe2fca1de5140f538e68f6981b27cf7f917e7a checks for pending
motion events and drops out of the FluxboxWindow::motionNotifyEvent() function
early if so. When the user does not use the opaque window movement method an
outline will be drawn to the screen. That outline was not cleaned correctly
with commit 79..
Mathias Gumz akira at fluxbox dot org
commit

6dca40aae6e0b0d923cc5eb7d18bb53c0a42482e

parent

52c374570ee5791a0b953f4ffc75082f216d1d1e

1 files changed, 6 insertions(+), 4 deletions(-)

jump to
M src/Window.cc → src/Window.cc 
@@ -2394,7 +2394,13 @@ // to activate it before doing the actual motionNotify code
     Fluxbox::instance()->keys()->doAction(me.type, me.state, m_last_pressed_button, context, &winClient(), me.time);
 
     if (moving) {
+
         XEvent e;
+
+        if (XCheckTypedEvent(display, MotionNotify, &e)) {
+            XPutBackEvent(display, &e);
+            return;
+        }
 
         // Warp to next or previous workspace?, must have moved sideways some
         int moved_x = me.x_root - m_last_resize_x;

@@ -2456,10 +2462,6 @@ // dx = current left side, dy = current top
         doSnapping(dx, dy);
 
         // do not update display if another motion event is already pending
-        if (XCheckTypedEvent(display, MotionNotify, &e)) {
-            XPutBackEvent(display, &e);
-            return;
-        }
 
         if (!screen().doOpaqueMove()) {
             parent().drawRectangle(screen().rootTheme()->opGC(),