[progress Communities] [progress Openedge Abl] Forum Post: Re: Using Stop-after

  • Thread starter Thread starter Laura Stern
  • Start date Start date
Status
Not open for further replies.
L

Laura Stern

Guest
Sorry, but if you're sitting in a dialog box, waiting for and processing user input, you cannot also be executing this code you are showing. Conversely, I could say, this code is basically in a busy loop, incrementing your vcounts variable over and over for 10 seconds. The UNDO, RETRY makes it appear as if you want this to happen forever!! (But luckily we will change that to UNDO, LEAVE as part of our infinite loop protection.) If it is doing that, nothing else will be going on during that 10 seconds. And therefore, your dialog box seems fairly useless. Where is this code relative to the WAIT-FOR and any trigger code you have for the dialog-box? Do you know that it is even running? Maybe you intended to have the STOP-AFTER around your WAIT-FOR statement? If so, you don't need your little busy loop in routine terminmess. But I don't think that will work anyway since I don't believe we abide by STOP-AFTER in input-blocking statements. Maybe you really want to use WAIT-FOR... PAUSE 10?

Continue reading...
 
Status
Not open for further replies.
Back
Top