Then Bill’s suggestion of setting a number of seconds within which the next click will be ignored might do the trick.
The technique I outlined is one I use to prevent a trigger from being fired again by an update to the row that triggered the code in the first place. Emmitt Dove Manager, Converting Applications Development Evergreen Packaging, Inc. [email protected] (203) 214-5683 m (203) 643-8022 o (203) 643-8086 f [email protected] From: [email protected] [mailto:[email protected]] On Behalf Of John Engwer Sent: Monday, March 02, 2009 4:01 PM To: RBASE-L Mailing List Subject: [RBASE-L] - Re: Mouse Happy Users Emmitt, Thanks for the suggestion but it produces the same result. It doesn’t process the second mouse click until the 1st click is finished processing and you have exited the EEP. At that point veep_running is NULL. John From: [email protected] [mailto:[email protected]] On Behalf Of Emmitt Dove Sent: Monday, March 02, 2009 3:28 PM To: RBASE-L Mailing List Subject: [RBASE-L] - Re: Mouse Happy Users John, You could, at the top of the eep, do something like this: SET VAR veep_running INTEGER IF veep_running IS NOT NULL THEN RETURN ELSE SET VAR veep_running = 1 ENDIF Then, at the end of the code: CLEAR VAR veep_running RETURN So the first click starts the eep. It should immediately set up a global variable indicating that it is executing. The second invocation should detect that and just quit. Finally, the first invocation will clear the variable when it is finished. Emmitt Dove Manager, Converting Applications Development Evergreen Packaging, Inc. [email protected] (203) 214-5683 m (203) 643-8022 o (203) 643-8086 f [email protected] From: [email protected] [mailto:[email protected]] On Behalf Of John Engwer Sent: Monday, March 02, 2009 3:22 PM To: RBASE-L Mailing List Subject: [RBASE-L] - Re: Mouse Happy Users Jan, I have tried disabling the DBGrid but the mouse clicks are stored in a buffer and as soon as you re-enable the DBGrid the EPP executes again. John From: [email protected] [mailto:[email protected]] On Behalf Of jan johansen Sent: Monday, March 02, 2009 3:04 PM To: RBASE-L Mailing List Subject: [RBASE-L] - Re: Mouse Happy Users John, I've done things like putting this in my on-clik eep. IF vSelectedRow IS NOT NULL THEN PROPERTY mydbgrid ENABLED 'FALSE' --do what I need to do here PROPERTY mydbgrid ENABLED 'TRUE' ELSE PROPERTY mdbgrid ENABLED 'TRUE' ENDIF RETURN Jan -----Original Message----- From: "John Engwer" <[email protected]> To: [email protected] (RBASE-L Mailing List) Date: Mon, 2 Mar 2009 14:57:33 -0500 Subject: [RBASE-L] - Mouse Happy Users In my applications I use a LOT of DBGrids that require a single mouse click to execute an EEP. Most users like the fact that one click is all that is required. However, are always a few users that when they see a list, they think you should click the mouse at least two or three times (I call them Mouse Happy Users). This causes the EEP to execute twice (or more), sometimes producing undesirable results or error conditions. I have tried warning messages “Single Click Only!” but they ignore the warning and keep clicking away. Does anyone have a way to suppress the mouse after one click that doesn’t require a lot of programming? John Engwer Engwer & Associates 2449 Scenic Ridge Drive North Huntingdon, PA 15642-2120 Phone: 412 751-2433 Email: [email protected] WWW.ENGWER.US
