nilix/fluxbox
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Fix regression in rendering the Window-Motion-Outline

Browse source 
Commit 79fe2fca1d 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..
This commit is contained in:
Mathias Gumz 2013-05-16 07:39:54 +02:00
parent 52c374570e
commit 6dca40aae6
1 changed files with 6 additions and 4 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

10
src/Window.cc
View file

@ -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(),