From: lahtonen@utu.fi   
      
   Jim Leonard wrote:   
      
      
   > To the OP:  Having mouse drawing code in an interrupt is only useful if   
   > 1. You know your redraw code will execute very very fast (before the   
   > next interrupt) and 2. you have complete control of the system.  You   
   > don't have that under XP, so I would recommend you don't use an   
   > interrupt-driven routine; instead, just poll the current mouse position   
   > and if it's different from last time (keep an oldx and oldy), then   
   > redraw.  No interrupts needed.   
   >   
      
   Very true. Thanks. I already keep oldx and oldy, as I obviously   
   cannot afford to wait for vertical retrace in a timer interrupt.   
   Your suggested approach will allow me to do what I need. The only   
   down side I see, is that I will need to call the redraw routine   
   from within the main program. This is, of course, no big deal,   
   as the main program will obviously be looping about waiting for   
   mouse input anyway!   
      
   I quite agree with Jason's assesment that if I can't redraw a   
   mouse cursor (keeping in mind that my slowesrt target platform is a 60   
   Mhz Pentium) fast enough, I really *should* get another hobby :-)   
   For the record. I write games with DPMI-target for the enjoyment   
   of myself (and my son) - so I can take certain liberties with   
   compatibility. Of course, my kid is approaching high school age,   
   so perhaps I should be worried about him picking up some bad programming   
   habits from his old man. Then again I was relatively impressed with   
   the game he wrote for my 42nd birthday (using my modeX graphics unit),   
   so may be I shouldn't worry too much.   
      
   Thanks to you all!   
      
   Jyrki   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)