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)
This commit is contained in:
parent
df6c013524
commit
491c2d74c1
|
@ -1027,7 +1027,7 @@ static inline int ensure_flag(int flags, int device_independent, int device_depe
|
||||||
} else {
|
} else {
|
||||||
location.x = lastpt.x + [e deltaX];
|
location.x = lastpt.x + [e deltaX];
|
||||||
location.y = lastpt.y - [e deltaY];
|
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 */
|
/* Convert coordinate system */
|
||||||
|
|
Loading…
Reference in New Issue