From 6dca40aae6e0b0d923cc5eb7d18bb53c0a42482e Mon Sep 17 00:00:00 2001
From: Mathias Gumz <akira at fluxbox dot org>
Date: Thu, 16 May 2013 07:39:54 +0200
Subject: [PATCH] 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..
---
 src/Window.cc | 10 ++++++----
 1 file changed, 6 insertions(+), 4 deletions(-)

diff --git a/src/Window.cc b/src/Window.cc
index 98486be7..12b37c94 100644
--- a/src/Window.cc
+++ b/src/Window.cc
@@ -2394,8 +2394,14 @@ void FluxboxWindow::motionNotifyEvent(XMotionEvent &me) {
     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;
         // save last event point
@@ -2456,10 +2462,6 @@ void FluxboxWindow::motionNotifyEvent(XMotionEvent &me) {
         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(),