Thanks to all for the input. I think it is our version that is broken. Without going into detail, we are stuck here for the time being.
Mike, I tried PROCESSMESSAGE and it worked on my test. Looks like the equivalent of DoEvents in VB It is very useful used sparingly Thanks a ton!, Dennis -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Mike Byerley Sent: Thursday, October 21, 2010 10:21 AM To: RBASE-L Mailing List Subject: [RBASE-L] - Re: Odd form behavior When I use the Kernel32 Sleep function with DLCall, I am able to replicate your issue. HOWEVER.... Since using the various methods to replicate the passage of time resulted in different outcomes, I was suspicious that it is a timing issue, so I added PROCESSMESSAGE immediately before the "Enable 'TRUE'" of the panels and the button queued button clicks were consumed without executing the EEP code attached to them. ----- Original Message ----- From: "Mike Byerley" <[email protected]> To: "RBASE-L Mailing List" <[email protected]> Sent: Thursday, October 21, 2010 10:48 AM Subject: [RBASE-L] - Re: Odd form behavior > What did you use for the pause for 5 seconds. I tried it with a "Pause > for 5" and still nothing from the second button, which is expected since > I'm not clicking on the "Pause for 5" popup which is modal at that point. > > > ----- Original Message ----- > From: "Dennis McGrath" <[email protected]> > To: "RBASE-L Mailing List" <[email protected]> > Sent: Thursday, October 21, 2010 10:31 AM > Subject: [RBASE-L] - Re: Odd form behavior > > > > > Sounded great to me. > I created a new form, filled it with a panel. > On the panel I put 2 buttons. > Button 1 disables the panel, pauses for 5 seconds and enables the panel. > Button 2 pops up a message box. > > I press button 1 and all looks disabled. > I click button 2. > When the five seconds is up everything enables. > The button 2 message pops up > > Dennis > > -----Original Message----- > From: [email protected] [mailto:[email protected]] On Behalf Of Mike > Byerley > Sent: Wednesday, October 20, 2010 9:22 PM > To: RBASE-L Mailing List > Subject: [RBASE-L] - Re: Odd form behavior > > Dennis, > That won't work at the form level, but if you put a panel on the form and > put all your controls on the panel, the panel can be enabled and disabled > to > effect everything in the container. > > > ----- Original Message ----- > From: "Dennis McGrath" <[email protected]> > To: "RBASE-L Mailing List" <[email protected]> > Sent: Wednesday, October 20, 2010 4:55 PM > Subject: [RBASE-L] - Re: Odd form behavior > > > Just running it cold by itself > > ________________________________ > From: [email protected] [mailto:[email protected]] On Behalf Of Jason > Kramer > Sent: Wednesday, October 20, 2010 3:01 PM > To: RBASE-L Mailing List > Subject: [RBASE-L] - Re: Odd form behavior > > If you are disabling the form in a while loop, try running the loop with > WHILEOPT set to OFF. > > Jason > > > Jason Kramer > > University Archives and Records Management > > 002 Pearson Hall > > (302) 831 - 3127 (voice) > > (302) 831 - 6903 (fax) > > On 10/20/2010 3:54 PM, Dennis McGrath wrote: > RBASE 7.6 > > On the click of a button: > > 1. disable the form > 2. run a lengthy process (refresh a listview) > 3. enable the form > > We click the button and then click anywhere on the form. > Because the form is disabled, nothing on the form should respond. > When the process finishes, and the form is enabled, it responds to the > bogus > clicks. > > It is obvious from the appearance of the form that it is not getting > disabled. > If I trace the code, the form disables/enables correctly > > Anyone know how to fix this? > > > Dennis McGrath > >
