You could add an instance variable that tracks the last time the button was clicked. If the two clicks are too close together, return from the event. I would use the timeGetTime Windows function which returns the current system time in milliseconds.

The very last line of code in the event will record the milliseconds in the instance variable.

The first line of code in the event will subtract the instance variable from the current value. If the difference is too small (under 100 for example) then Return.

Function ulong timeGetTime ( ) Library "winmm.dll"

https://learn.microsoft.com/en-us/windows/win32/api/timeapi/nf-timeapi-timegettime

Hi Everyone;

  After extensive testing using a Ribbon Bar; Picture Button; Command Button and CB within a DW control  -  I have now opened a new support ticket for issues around these controls on properly handling a double click. I have now tested my Test Case in PB 2019R3 through PB 2022 R2 beta and on W10 & W11.

  You can read all about my reported bug in ticket # 10581

Regards ... Chris

Hi Chris, thanks!

I have a couple of questions.

How critical is it to add this new code into its own event handler? I tried it both ways and I can't see any difference. Is it just good practice or what?

Can you give me the theory on what is happening? Here's my attempt at it: 

1) First click happens

2) Click handler is entered

3) Button is disabled

4) Other code in click handler runs. Some time while this is happening, the second click occurs (over the disabled button).

5) The Yield() allows the second click to "process", which since it is over a disabled button, is a do-nothing. 

6) Not exactly sure what the Message.Processed = true is doing.

     (Note: I tried running with and without Message.Processed = true and could not detect any difference in behavior)

7) Button is re-enabled and (original) click event handler finishes. 

If this is right or close, then I see there may be a race condition happening: maybe the event handler takes 0.5 seconds (there is some database manipulation going on in it). The time between clicks might be 0.4 seconds, in which case the added code should effectively make that second click go away. 

But what if the time between clicks is 0.51 seconds? Then the handler is finished, and the second click will take place over whatever control happens to be there, same as what I have now. Is that correct?

@Chris,

here's the adapted sample app with your suggested code. See attached. PB2019 R3 build 2797

regards

Hi Troy / Miguel;

  I have this working very well & it's really simple to code.

• Create a User Event on the CB (ie: oe_enable)
• Post the UE on the Clicked event ...

THIS.enabled    =    FALSE
THIS.POST Event oe_enable( )

• In the UE run the following code ...

Message.Processed  = TRUE
Yield ( )
THIS.enabled = TRUE

Note1: that this can be easily adapted in an ancestor CommandButton or PictureButton control. Also, no fancy timers, sleepers, switches, etc needed.

Note2: Tested on PB 2019R3, 2021, 2022 on W10 & W11.

Note3: PB 2019R3 test case now attached.

Regards ... Chris

Ok,

You're absolutely right. In older powerbuilder versions this would have probably worked :(

Ignore the picture, I've copied this from another sample app.

The only important thing are the 2 instance variables and the command button.

I've build in a delay to execute or not the button. I've used 1000 msecs of delay to rather execute the script or not, but you might want to make that delay bigger or smaller.

See the attached sample app. PB2019 R3.

Hi,

Have you tried to do:

This.Enabled = false at the beginning of the clicked event?

At the end of the event, you'd then do a:

This.Enabled = true

regards.