darcs patch: clear out motion events when processing one motion event.

On my laptop anyhow (over six years old) this is completely necesary for
adequate performance when something expensive is being done in the drag
loop. And it's harmless, so far as I can tell.
David
Sun Aug 19 17:23:51 PDT 2007 David Roundy

On Sunday 19 August 2007 19:26:53 David Roundy wrote:
On my laptop anyhow (over six years old) this is completely necesary for adequate performance when something expensive is being done in the drag loop. And it's harmless, so far as I can tell.
David
Sun Aug 19 17:23:51 PDT 2007 David Roundy
* clear out motion events when processing one motion event. This is important if the hook is slow (e.g. try adding "float w" to the window-dragging hook), as it allows xmonad to keep up with the motion of the mouse.
Applied, thanks. IIRC, we used to do this, perhaps it was removed in the recent dragging refactor?

On Mon, Aug 20, 2007 at 03:57:38PM -0500, Spencer Janssen wrote:
On Sunday 19 August 2007 19:26:53 David Roundy wrote:
On my laptop anyhow (over six years old) this is completely necesary for adequate performance when something expensive is being done in the drag loop. And it's harmless, so far as I can tell.
David
Sun Aug 19 17:23:51 PDT 2007 David Roundy
* clear out motion events when processing one motion event. This is important if the hook is slow (e.g. try adding "float w" to the window-dragging hook), as it allows xmonad to keep up with the motion of the mouse. Applied, thanks.
IIRC, we used to do this, perhaps it was removed in the recent dragging refactor?
It could be, but I don't think so. I copied the old code pretty literally. -- David Roundy http://www.darcs.net
participants (3)
-
David Roundy
-
David Roundy
-
Spencer Janssen