From 491c2d74c12d7f9bc9f31b427ece04e049ebff5a Mon Sep 17 00:00:00 2001 From: Jeremy Huddleston Date: Sat, 1 Aug 2009 12:43:14 -0700 Subject: [PATCH] XQuartz: Use mouseLocation rather than locationInWindow when setting lastpt I don't understand the *why* ... I just see that it works better this way for games like Quake2 through wine. It *should* be better the other way, but somehow it's not. I guess this will go in my list of puzzles to unravel. (cherry picked from commit 65ae2d00e1a53f97f2ff9522406ab69d50bf3199) --- hw/xquartz/X11Application.m | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/hw/xquartz/X11Application.m b/hw/xquartz/X11Application.m index 9d6ee71a5..5d28132bf 100644 --- a/hw/xquartz/X11Application.m +++ b/hw/xquartz/X11Application.m @@ -1027,7 +1027,7 @@ static inline int ensure_flag(int flags, int device_independent, int device_depe } else { location.x = lastpt.x + [e deltaX]; location.y = lastpt.y - [e deltaY]; - lastpt = [e locationInWindow]; + lastpt = [NSEvent mouseLocation]; // [e locationInWindow] gives us the "unfixed" location when our cursor is fixed. This bugs things like quake } /* Convert coordinate system */