I don't know what the definition of "a lot" is, John, but within the EEP,
you could set a variable on the first click, and test it on each click, and
if it was already set, ignore the processing. Of course, then you have to
have a way to "unset" the variable in case they really do come back and
click again later.
Oh, maybe that's the definition of "a lot!" Okay, use a timer. After 3
seconds, they can click again.
SET VAR vAllowSecs INT = 3
SET VAR vLastClicked DATETIME
IF vLastClicked IS NULL THEN
SET VAR vLastClicked = .#NOW
ELSE
IF (AddSec(.vLastClicked, .vAllowSecs)) < .#NOW THEN
GOTO lbExit
ELSE
SET VAR vLastClicked = .#NOW
ENDIF
ENDIF
-- rest of EEP code
LABEL lbExit
RETURN
On Mon, Mar 2, 2009 at 2:57 PM, John Engwer <[email protected]> wrote:
> 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 <http://www.ENGWER.US>
>
