Hello Razzak, Thanks for the primer on PROCESSMESSAGE. Your explanation should be added to the R:BASE X help :-)
A sample showing the placement of the EEP code within the pau 3 block would be great. Thank you so much, Claudine -----Original Message----- From: rbase-l@googlegroups.com [mailto:rbase-l@googlegroups.com] On Behalf Of A. Razzak Memon Sent: Wednesday, October 03, 2018 9:11 PM To: rbase-l@googlegroups.com Subject: Re: [RBASE-L] - NOT RESPONDING Hi Claudine, That is a very common symptom when performing long running time-consuming routines. There are a few techniques to improve such performance. 01. Use of PROCESSMESSAGE command in WHILE ... ENDWHILE loop. While process a time-consuming routine and displaying the PAUSE 3 message with GAUGE, you also implement the the use of PROCESSMESSAGE command that processes messages that are currently in the windows message queue. The PROCESSMESSAGE can help in the GUI part to avoid the "Not responding" behavior in Windows operating systems. A common use of PROCESSMESSAGE is in long WHILE loops. PROCESSMESSAGE may be called in each loop iteration to give the GUI time to process the pending Windows messages. For a loop that only does data processing, PROCESSMESSAGE can also be used. It is advised to disable GUI update settings like UINOTIF before entering the loop with PROCESSMESSAGE, to counter some side-effects of PROCESSMESSAGE. It is also important to not overuse PROCESSMESSAGE. Use the command only in places where it is necessary for the GUI to "breath" during a long running task. 02. Use of NO_FOCUS option in PAUSE 3 and PAUSE 4 Commands NO_FOCUS option specifies the pause will not be focused when displayed, which can be used to possibly prevent an interruption in the focus transition in an active form. For further details and sample examples, please refer to HELP PROCESSMESSAGE and HELP PAUSE options. Please feel free to reach out to me if you need any examples to illustrate the use of such techniques. Hope it helps! Very Best R:egards, Razzak At 09:39 PM 10/3/2018, Claudine Robbins wrote: >I've meant to ask about this for quite some time. When there is a >somewhat lengthy process, "Not Responding" will occasionally pop up >at the top of the screen. Users often click on the x to exit the >screen but the process is really still working and just waiting will >let it complete. > >What causes this and can it be avoided? > >TIA, > >Claudine -- For group guidelines, visit http://www.rbase.com/support/usersgroup_guidelines.php --- You received this message because you are subscribed to the Google Groups "RBASE-L" group. To unsubscribe from this group and stop receiving emails from it, send an email to rbase-l+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- For group guidelines, visit http://www.rbase.com/support/usersgroup_guidelines.php --- You received this message because you are subscribed to the Google Groups "RBASE-L" group. To unsubscribe from this group and stop receiving emails from it, send an email to rbase-l+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
