Re: [dev] [dwm] Avoid requesting MotionNotify events

2016-07-16 Thread Alexander Monakov
On Sat, 16 Jul 2016, FRIGN wrote: > nice work soldier! Can you elaborate on how you measured the syscalls > per second? I simply invoked strace in the following fashion (bash): $ sleep 1; strace -cfp `pidof dwm` & sleep 1; kill % (this wouldn't be accurate at very high syscall rates due to s

Re: [dev] [dwm] Avoid requesting MotionNotify events

2016-07-16 Thread FRIGN
On Sat, 16 Jul 2016 14:33:18 +0300 (MSK) Alexander Monakov wrote: Hey Alexander, > A while ago dwm started requesting MotionNotify events from the X > server (that wasn't always the case). This was added when > focus-follows-mouse was implemented for monitors (in addition to > windows) in 2011 b

Re: [dev] [dwm] Avoid requesting MotionNotify events

2016-07-16 Thread Alexander Monakov
On Sat, 16 Jul 2016, Staven wrote: > On Sat, Jul 16, 2016 at 02:33:18PM +0300, Alexander Monakov wrote: > > This causes lots of useless communication between the X server and dwm every > > time the mouse pointer is moved, even when nothing could possibly change as > > a result (e.g. if Xinerama is

Re: [dev] [dwm] Avoid requesting MotionNotify events

2016-07-16 Thread Staven
On Sat, Jul 16, 2016 at 02:33:18PM +0300, Alexander Monakov wrote: > This causes lots of useless communication between the X server and dwm every > time the mouse pointer is moved, even when nothing could possibly change as > a result (e.g. if Xinerama is not compiled in, or only one monitor is >

[dev] [dwm] Avoid requesting MotionNotify events

2016-07-16 Thread Alexander Monakov
Hi, A while ago dwm started requesting MotionNotify events from the X server (that wasn't always the case). This was added when focus-follows-mouse was implemented for monitors (in addition to windows) in 2011 by commit b5068e32e9. This causes lots of useless communication between the X server an