Ahhh - wouldn't do that if I were you. Your program's CPU usage will max out your processor. I'd use a timer if I was that stuck but even then, it's hardly ideal...
Cardinal rule of application programming: don't check if nothing has changed = don't do something unless an event has happened = always use WaitEvent(). ;-) True, there aren't events (at the moment) which show you this particular thing has changed but even using a timer to check every 100 milliseconds would be better than your current loop which is just wasting billions of CPU cycles.
There may be a few tricks up my sleeve with the current development version of MaxGUI I'm testing - I'll let you know more once it's available on SVN, but it should help you out somewhat...
Btw, when posting code, use the [code ] or [codebox ] tags - see the following page for more info: What are the forum codes?. I've edited your original post to show you how its done... ;-)
Cardinal rule of application programming: don't check if nothing has changed = don't do something unless an event has happened = always use WaitEvent(). ;-) True, there aren't events (at the moment) which show you this particular thing has changed but even using a timer to check every 100 milliseconds would be better than your current loop which is just wasting billions of CPU cycles.
There may be a few tricks up my sleeve with the current development version of MaxGUI I'm testing - I'll let you know more once it's available on SVN, but it should help you out somewhat...
Btw, when posting code, use the [code ] or [codebox ] tags - see the following page for more info: What are the forum codes?. I've edited your original post to show you how its done... ;-)