Hi Antonio
Is the following correct:
When your application calls CursorWait() and the hour glass cursor is displayed, this DISABLES all keyboard and mouse clicking in your application until you call CursorArrow()
Can you please confirm the above or explain better
Thanks
Peter
Peter,
No, not at all. The keyboard and mouse events keep being processed, unless you 
isable() the window.
Antonio
The cursorwait hourglass cursor does not let you click on anything so in that way it seems to disable clicking
Thanks
Peter
Peter,
What process are you doing in your application after you call CursorWait() ?
The process may be consuming all the CPU cycles and thats why it seems that events are not processed. Turning one cursor into another, will not make the application stop processing events.
Antonio
The proces is an intensive loop through a dbf, so you are probably correct
I am confused because sometimes they seem to work and other times they seem to get reset to the default cursor
I will try read up on them
Thanks for your assistance
Peter
Peter,
If you don't want to process any events, simply isable() the window. When you are done, :Enable() it.
Also if you do an intensive loop, you should call SysRefresh(), at certain places, to let Windows process its pending messages, or Windows will stop responding.
