GUI (ControlClick) Oddness

[JohnOne]

scenario:

I compile this code...

GUICreate('mytest', 300, 100)
$button = GUICtrlCreateButton('button', 130, 40)
GUISetState()

While 3
    Switch GUIGetMsg()
        Case $button
            MsgBox(0, 'Button', 'Pressed')
        Case -3
            Exit
    EndSwitch
WEnd

...and execute the compiled script.

Then run this code from scite...

ControlClick('mytest', '', '[CLASS:Button; INSTANCE:1]')

... and this is where it's odd.

The GUI button will only be clicked once in every three attempts of running the script.

First run activates the GUI, second does nothing and the third clicks the button, and then we're full circle.

Is my computer going mad, or can anyone reproduce same?

Edited March 17, 2014 by JohnOne

[Melba23]

JohnOne,

I get the same "1 in 3" result as you. The Help file mentions that ControlClick does need some controls to be in the active window - and if I add a WinActivate("mytest") line first the button fires every time, so this must be one of them.

M23

[JohnOne]

Hmm, so it does, wonder why the third time fires without it being activated first though.

EDIT:

well once winactivate has been used, and you comment it out, it fires every time too.

EDIT:

that is of course until the gui exe is restarted

Edited March 16, 2014 by JohnOne

[mikell]

Funny test

ControlClick('mytest', '', '[CLASS:Button; INSTANCE:1]')
ConsoleWrite(WinGetTitle("[active]") & @crlf)

[JohnOne]

I'm beginning to suspect a bug in ControlClick()

The above test show how odd it is, and I now doubt it's GUI oddness, cause I've never had an issue clicking a simple au3 button before.

Repeat the test but this time ensure the test GUI is minimized and the click works every time.

EDIT:

Having said that, It's also possible that a windows update has broken it.

I'd be interested to hear if this weirdness occurs in xp and vista, I'm on 7 x86.

Edited March 17, 2014 by JohnOne

[mikell]

Weird too on my old XP SP3

Edit

v. 3.3.10.0

Edited March 17, 2014 by mikell

[JohnOne]

Tried with 3.3.8.1 and latest beta.

[mLipok]

Hmm, so it does, wonder why the third time fires without it being activated first though.

 

Try this:

$hwnd = GUICreate('mytest', 300, 100)
$button = GUICtrlCreateButton('button', 130, 40)
WinSetOnTop($hwnd,'',1)
GUISetState()

While 3
    Switch GUIGetMsg()
        Case $button
            MsgBox(0, 'Button', 'Pressed')
        Case -3
            Exit
    EndSwitch
WEnd

now you can better see what happen.

ps.

Win7Pro x64 - the same results

EDIT: typo

Edited March 17, 2014 by mLipok

[JohnOne]

mLipok does it work as it should if GUI is minimized?

[JohnOne]

I was about to test on a VM I have not updated for a while, but I've forgotten the password, and don't think it can be removed like it can on a normal computer

[mLipok]

mLipok does it work as it should if GUI is minimized?

 

Yes

 

JohnOne,

I get the same "1 in 3" result as you. The Help file mentions that ControlClick does need some controls to be in the active window - and if I add a WinActivate("mytest") line first the button fires every time, so this must be one of them.

M23

 

and....

I'm beginning to suspect a bug in ControlClick()

 

This is not problem with WinActive state.

This is a problem with ControlClick

try this:

$hwnd = GUICreate('mytest', 300, 100)
$button = GUICtrlCreateButton('button', 130, 40)
WinSetOnTop($hwnd,'',1)
GUISetState()

While 3
    Switch GUIGetMsg()
        Case $button
            MsgBox(0, 'Button', 'Pressed')
        Case -3
            Exit
    EndSwitch
WEnd

and this:

ControlFocus('mytest', '', '[CLASS:Button; INSTANCE:1]')
ControlClick('mytest', '', '[CLASS:Button; INSTANCE:1]')

How you can see now it works every time regardless of whether the window is active.

For me it deserves to be Tracked as Feature Request, or even as a Bug.

 

EDIT:

TrackTicket: ... because if properly indicated on the Button, regardless of the status window ControlClick should work properly, yet in effect after the "click" , focus will be set.

Edited March 17, 2014 by mLipok

[JohnOne]

But what if a windows update has caused the issue, I don't think it would qualify as a bug.

I've tested it on other windows such as IE too and the problem persists, where it's a little different and click only works second time around.

[mLipok]

But what if a windows update has caused the issue, I don't think it would qualify as a bug.

So only feature request.

My opinion is that if someone wants to click using this function, the function should click properly in every situation, especially since the end result will be exactly the same if I physically click with the mouse.

Edit:

unless, the current effect is intentional, maybe it has to serve some specific cases.

Edited March 17, 2014 by mLipok

[mikell]

We can assume that this issue is known since ages as we always could read in the helpfile

"Use the WinActivate() function to force the control's window to the top before using ControlClick()."

[JohnOne]

I don't believe so, this is new and unexpected behaviour to me.

I'm aware that some controls need focus, but I've used this many times on the very controls I'm trying it on now, and it's acting all weird.

Edited March 17, 2014 by JohnOne

[mLipok]

try this:

#include <GUIConstantsEx.au3>

$hwnd = GUICreate('mytest', 300, 100)
$button = GUICtrlCreateButton('button', 40, 40)
$button2 = GUICtrlCreateButton('button2', 100, 40)
$TrayTip = GUICtrlCreateCheckbox('TrayTip ?', 150, 40)
WinSetOnTop($hwnd, '', 1)
GUISetState()

Global $iCount = 0
GUICtrlSetState($button2, $GUI_FOCUS)

While 3
    Switch GUIGetMsg()
        Case $button
            $iCount += 1
            If GUICtrlRead($TrayTip) = $GUI_CHECKED Then
                TrayTip('Button', 'Pressed #' & $iCount, 1)
            Else
                MsgBox(0, 'Button', 'Pressed #' & $iCount)
            EndIf
        Case -3
            Exit
    EndSwitch
WEnd

You will notice that with TrayTip this problem do not appear.

[mLipok]

We can assume that this issue is known since ages as we always could read in the helpfile

"Use the WinActivate() function to force the control's window to the top before using ControlClick()."

The fact that this is known since ages, do not mean this is intentional.

 

 

I don't believe so, this is new and unexpected behaviour to me.

 

I'm aware that some controls need focus, but I've used this many times on the very controls I'm trying it on now, and it's acting all weird.

 

I found something interesting and another one  

[mikell]

The fact that this is known since ages, do not mean this is intentional.

Oh I agree ! 

But if the only answer is the use of WinActivate, that probably means that the solution depends on different various circumstances, so the only reliable (?) way should be - as you said before - to include a ControlFocus into the ControlClick command

BTW thanks for the 2 funny links 

[mLipok]

BTW thanks for the 2 funny links 

 

I wonder if JohnOne also considers it "funny".

I hope he have a sense of humor.

[JohnOne]

I was looking for a link with those threads and this at first.