hw/xwin: Fix winEnqueueMotion() for change in miPointerSetPosition()
Commit 3b36fd1b49
changed miPointerSetPosition()
to take co-ordinates as doubles, not ints, so this code as it stands is now wrong
(if it ever was correct in the first place :-))
It's unclear that we can safely promote x,y to doubles, apply miPointerSetPosition()
which potentially constrains the cursor, and then convert back to ints.
Fortunately, this whole dance seems to be unnecessary, and we can simply remove the
call to miPointerSetPosition() entirely, and just QueuePointerEvents() like any other
input driver.
Signed-off-by: Colin Harrison <colin.harrison@virgin.net>
Reviewed-by: Jon TURNEY <jon.turney@dronecode.org.uk>
This commit is contained in:
parent
ced9db6595
commit
80c073352a
|
@ -356,15 +356,12 @@ winMouseButtonsHandle (ScreenPtr pScreen,
|
|||
/**
|
||||
* Enqueue a motion event.
|
||||
*
|
||||
* XXX: miPointerMove does exactly this, but is static :-( (and uses a static buffer)
|
||||
*
|
||||
*/
|
||||
void winEnqueueMotion(int x, int y)
|
||||
{
|
||||
int valuators[2];
|
||||
ValuatorMask mask;
|
||||
|
||||
miPointerSetPosition(g_pwinPointer, POINTER_RELATIVE, &x, &y);
|
||||
valuators[0] = x;
|
||||
valuators[1] = y;
|
||||
|
||||
|
|
Loading…
Reference in New Issue
Block a user