🚀 go-pugleaf

I've been having a pesky problem with a program I'm writing that
uses a separate thread, with a MouReadEventQue loop, to
respond to mouse movements.  When this program runs in full 
screen mode, I need at times to temporarily turn off the mouse
pointer in response to certain keystrokes.  The problem is that 
when the user is entering these keystrokes, the mouse thread
is blocking on the MouReadEventQue, which means that calls to
MouRemovePtr don't work (they return a 121), and the next time
the user moves the mouse, it leaves a 'dropping' at its old
location.

I had hoped to find a solution by examining the code for the
WORMS sample program that comes with the 2.0 toolkit, but, alas,
WORMS also seems to have this problem!  Start it in full screen,
move the mouse pointer to one of the letters at the top of the
screen, and quit by keying the letter E.  Not only does it leave
a mouse dropping, but you will find that the mouse is locked out
if you try to restart the program in the same session!  The 
second problem is solveable by doing a MouClose in ExitList
processing, but I can't figure out how to eliminate the mouse
droppings.  This isn't a problem if you run the program in
a window, but my users want the option of running in full screen
mode.

OS/2 gurus, can you help this newbie programmer?  I need a 
solution that works in either full screen or windows.  Thanks
in advance!

-- 
Rose Marie Smith // Univ. of Wisconsin - Madison
rose.smith@mail.admin.wisc.edu