I'm attempting to use the WM_MOUSEMOVE message to control the mouse cursor. If the mouse if over a certain hot spot, I call SetClassLong to change that window's class mouse pointer to something else. A problem results when the mouse is S L O W L Y moved off the hot spot. I can see in debug messages that the pointer leaving the hot spot is detected, and the class mouse pointer is changed. However, this change is not seen on the screen until the mouse is again moved. Is there soem update API or message I could be calling to prevent this annoyance?
Posted on 2001-04-13 00:00:00 by Ernie
Ernie, The usual trick is to use SetCursor() after you have set the class cursor to NULL, then after the condition ends that requires the different cursor, you reset the class cursor back to the original. Regards, hutch@pbq.com.au
Posted on 2001-04-13 02:44:00 by hutch--