Lew Schwartz wrote: > This is an old story: > I have a form that initiates a lengthy batch processing loop. > The command buttons on the form are unclickable while the loop is > running so I set escape on, test for inkey() in the loop and exit if the > user presses escape.... This get me back to my read events statement and > the buttons become alive again. This method is as old as the hills and > somewhat inelegant. > Are there any other or newer suggestions? > One (at least) - before entering the loop (when setting up the inkey) disable the command button(s) - this will give the user a visual cue that they are (temporarily) unavailable > -Lew > > [excessive quoting removed by server]
_______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
