Button Double Click Problem

[Topher]

I have a script that at its heart is basically this

Func _WM_COMMAND($hWnd, $Msg, $wParam, $lParam)
    Local $nNotifyCode = BitShift($wParam, 16)
    Local $nID = BitAND($wParam, 0x0000FFFF)
    Local $hCtrl = $lParam
    If $nNotifyCode = $BN_DBLCLK And $nID = $hButton Then
       ; do stuff
        Return 0
    EndIf
    Return $GUI_RUNDEFMSG
EndFunc

The script does different things depending on whether the button is clicked or double clicked.

The problem I am having is that if I double click, it registers as both a single click and double click.

How do I suppress the single click if there is a double click?

[Chimaera]

Can you make a delay or maybe timer after the first click and increase it until its longer than the gap between the double click?

Just what popped into my head dunno if its possible

[Topher]

Actually speeding up the routines was the original reason for adding the double click.

I don't comprehend why that would effect the double triggering anyway.

Edited March 7, 2012 by Topher

[Chimaera]

ok bear in mind i was just speaking out loud.

i was thinking one click + time delay of prob only a sec

and double click with no time delay

the one click would be more [in time] than a double click which happens in less than a sec by a long way which would separate them and make them identifiable

Cant say it will work...

I'm sure the big boys will be along soon with better offerings

Edited March 7, 2012 by Chimaera

[BrewManNH]

Where in your code are you checking for the single click? If you put the single click detection into the windows message routine, and you put the double click detect first, does it work?

[Melba23]

Topher,

This thread might prove useful.

M23

[Topher]

Where in your code are you checking for the single click? If you put the single click detection into the windows message routine, and you put the double click detect first, does it work?

Sing click is being picked up via the GUIGetMsg() function.

If I am reading the question right. Are you saying I can detect the single click in the WM_COMMAND system?

If so what would I be searching for?

[BrewManNH]

Look in my signature for the GUIRegisterMsg demo thread I started. There's a lot of references in it that could be helpful.

[Topher]

It took me awhile but I finally felt I understood that script and adapted it to my program successfully.

But this created a new problem. (sigh)

In my script I have several buttons (it is a game) in a row which are clicked in either single or double clicks.

This can in some cases be rather rapid.

The routines above do not store all the clicks but rather ignore the ones that come while it is working on another button.

[Melba23]

Topher,

Is this a game you are writing in AutoIt or an external game you are automating?

M23

[Topher]

Topher,

Is this a game you are writing in AutoIt or an external game you are automating?

M23

It is in Autoit (I always forget about the automation side of Autoit as I never have need of it or I would have mentioned that)

[Melba23]

Topher,

Then assuming each click/doubleclick runs code within a function, you might find the Interrupting a running function tutorial in the Wiki of interest.

M23

[Topher]

Thank you for your swift answer.

There is a lot to process there (I'm persistent but slow)

Thank you for pointing me in a direction.

[Topher]

Actually that was quite straight forward and I knew most of it, so that made it easier to digest.

The problem I am having is that the routine which detects the double click (and makes sure not to have a double click also being a single click) by its nature destroys the single click and therefore any single clicks after it in the double click waiting period. For the life of me I don't even have the faintest hint of how to get around this.