nanogui@linuxhacker.org

On 02-Mar-00, Greg Haerr wrote:
>: >From an examination of the code, I think that the problem lies with
>: the buffering of mouse movements in drivers/mou_ser.c. When the mouse
>: is read by GdReadMouse() it can leave data in the buffer which will
>: not be processed until the next time the mouse is physically moved.
>: I have made the following change to nanox/srvevent.c and mwin/winevent.c
>: which causes all buffered data to be processed whenever a mouse event
>: occurs. This appears to fix the problem (I suspect that the only reason
>: I saw it in the first place is that the Prisma is very slow at displaying
>: bitmaps so mouse movements could get ahead of the cursor display updates).
>: 

>What version of Microwindows are you running?  Microwin or Nano-X
>API?  I changed an if statement to a while loop in the main GsSelect()
>code that also might help with this.

I am using the final 0.87 release.
The delayed-action effect occured with both the Microwin and Nano-X demos,
they use very similar code to read mouse events (mwin/winevent.c and
nanox/srvevent.c).

[ snip ]

Thanks,

George