summary refs log tree commit diff
diff options
context:
space:
mode:
authorokan <okan>2019-08-13 18:45:38 +0000
committerokan <okan>2019-08-13 18:45:38 +0000
commit781af9c998b109ffc21569afcca8e0f850c4ddbf (patch)
tree8507eaba196986a2f5a098ec5b1d9206f6be7767
parent6131e36f8a838aa54ed687dc08b387bceeb70fdf (diff)
downloadcwm-781af9c998b109ffc21569afcca8e0f850c4ddbf.tar.gz
cwm-781af9c998b109ffc21569afcca8e0f850c4ddbf.tar.xz
cwm-781af9c998b109ffc21569afcca8e0f850c4ddbf.zip
Because cwm warps the pointer during a client move (to stay within the client),
there's a window of time where an expose or enternotify event will get
generated for a lower client; use a hammer and drain events after keyboard
move/resize, until such a time that cwm doesn't warp the pointer.  Behavior
noticed by kn.

ok kn@
-rw-r--r--kbfunc.c2
1 files changed, 2 insertions, 0 deletions
diff --git a/kbfunc.c b/kbfunc.c
index 03a5d79..b171231 100644
--- a/kbfunc.c
+++ b/kbfunc.c
@@ -142,6 +142,7 @@ kbfunc_client_move_kb(void *ctx, struct cargs *cargs)
 
 	client_move(cc);
 	client_ptr_inbound(cc, 1);
+	XSync(X_Dpy, True);
 }
 
 static void
@@ -230,6 +231,7 @@ kbfunc_client_resize_kb(void *ctx, struct cargs *cargs)
 
 	client_resize(cc, 1);
 	client_ptr_inbound(cc, 1);
+	XSync(X_Dpy, True);
 }
 
 static void