I can replicate this, but I think it's expected behavior. First panel has bit button with:
PROPERTY paneltwo ENABLED 'FALSE' PAUSE FOR 5 PROPERTY paneltwo ENABLED 'TRUE' RETURN Second panel has bit button with: SET VAR vnewcount INTEGER = 0 WHILE vnewcount < .vcount THEN SET VAR vnewcount = (.vnewcount + 1) ENDWHILE RECALC VARIABLES RETURN Outside the panels, I have two variable edits, one for vcount and one for vnewcount. Edit using the form, type a number in vcount, then press the bit button in panel one. Immediately press the button in panel two, which doesn't appear to press. When the five seconds is up, the variable vnewcount shows the same number as vcount. Here's my theory.... could be wrong of course. Isn't the PAUSE FOR 5, just saying wait 5 seconds before doing the next step? It's not saying don't do the next thing ever, just wait five seconds. It's got the next command, enabling the second panel, already queued - it's just waiting to do it. It's already queued when you click on the button in panel two (which then is queued as well.) You need to move the enabled 'true' step so it's a separate action somehow. -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Mike Byerley Sent: Thursday, October 21, 2010 10:38 AM To: RBASE-L Mailing List Subject: [RBASE-L] - Re: Odd form behavior I tested the following: Variable form with two panels, a variable edit and two buttons, one a push button and one a speed button. the variable edit and the pushbutton are on panel 1 and the speed button is on panel two. The pushbutton has code: --trace SET VAR vi INTEGER = 0 --PROPERTY RBASE_FORM enabled 'false' PROPERTY pnlone enabled 'false' PROPERTY pnltwo enabled 'false' RECALC VARIABLES IF vcount > 0 THEN WHILE vi <> .vcount THEN OUTPUT SCREEN WRITE 'x' OUTPUT SCREEN SET VAR vi = (.vi + 1) ENDWHILE PAUSE 2 USING 'done' ENDIF --PROPERTY RBASE_FORM enabled 'true' PROPERTY pnlone enabled 'true' PROPERTY pnltwo enabled 'true' SET VAR vcount = 0 RECALC VARIABLES RETURN The variable edit has the value of the loop iteration so I can set the length time of the loop to longer amounts. While the loop is running, I clicked in each separate test increasing number of clicks from one to four and no mouse clicks were Queued while the panels were disabled. I am unable to replicate your conditions you describe (using this test). ----- Original Message ----- From: "Lena Dammstrom" <[email protected]> To: "RBASE-L Mailing List" <[email protected]> Sent: Thursday, October 21, 2010 9:28 AM Subject: [RBASE-L] - Re: Odd form behavior Hi I'm Lena and I work with Dennis M.... Actually I have a Tab Control and 3 panels on the first tab control. First panel has Variable RadioGroup(s) and Variable Lookup ComboBox Second panel has some Bit Buttons and variable edit controls Third panel has variable lookup up ListView - which is what I am populating, and while that populates I want to disable the other stuff. I set panels 1 and 2 as Property compId Enabled 'FALSE' I can see the controls on these panels are disabled (goes gray) While the ListView is processing, I click on the grayed out controls. After listview process is done, I enable the panels and all grayed out click events gets processed. I thought when controls are disabled, the mouse events on the controls are ignored, not buffered and completed once controls are enabled. Confused.... Any insight? Regards Lena -----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 DISCLAIMER: This electronic message together with any attachments is confidential. If you are not the intended recipient, do not copy, disclose or use the contents in any way. Please also advise us by return e-mail that you have received the message and then please destroy. Evergreen Packaging is not responsible for any changes made to this message and / or any attachments after sending by Evergreen Packaging. We use virus scanning software but exclude all liability for viruses or anything similar in this email or any attachment.
