diff options
| author | Brian <brian@yutani.localnet.net> | 2007-03-30 16:05:46 -0600 |
|---|---|---|
| committer | Brian <brian@yutani.localnet.net> | 2007-03-30 16:05:46 -0600 |
| commit | ebdc8ce5c108dc3b6b0004e7c7939d1a5bef8676 (patch) | |
| tree | c57b62a810836dd460009e97a3b3a2c724022809 /hw/dmx/dmxcursor.c | |
| parent | 3c7413e0c2f87e154aa8aa4a83bd585a6d1091e8 (diff) | |
Checkpoint DMX updates: things are working much better now, but still not 100% right.
Use new dmxCoreMotion2() function which enqueues motion events with
GetPointerEvents()/mieqEnqueue().
The clipAxis() code in GetPointerEvents() is causing some grief. The
limits seem to have always been (0,0) according to the original calls
to InitValuatorAxisStruct() in dmxinputinit.c.
Terrible hack for now: Call InitValuatorAxisStruct() with hard-coded max
values of 1280 (my screen width).
Diffstat (limited to 'hw/dmx/dmxcursor.c')
| -rw-r--r-- | hw/dmx/dmxcursor.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/hw/dmx/dmxcursor.c b/hw/dmx/dmxcursor.c index 11c89d822..a7d9378b0 100644 --- a/hw/dmx/dmxcursor.c +++ b/hw/dmx/dmxcursor.c @@ -889,7 +889,7 @@ static void dmxSetCursor(ScreenPtr pScreen, CursorPtr pCursor, int x, int y) gx = start->rootXOrigin + x; gy = start->rootYOrigin + y; if (x && y && (GX != gx || GY != gy)) - dmxCoreMotion(gx, gy, 0, DMX_NO_BLOCK); + dmxCoreMotion(NULL, gx, gy, 0, DMX_NO_BLOCK); if (!start->over || !dmxCursorDoMultiCursors || start->cursorNotShared) { _dmxSetCursor(pScreen, pCursor, x, y); |