ControlSend script blocking bug?

[milos83]

In this reproducer the ControlSend will block the script from finishing.

I do know that control with the ID of 0 probably doesn't exists, but nevertheless, this is unexpected behaviour.

Tested in Win 10
Autoit: v3.3.14.2

$gGUIDummy = GUICreate("")

Run("notepad.exe")

$HWND = WinWait("Untitled - Notepad")

WinActivate($gGUIDummy)

ControlSend($HWND, "", 0, "!f") ;control Id 0 is the issue here

Edited January 17, 2018 by milos83

[jdelaney]

Use this instead:

WinMenuSelectItem

Sends generally don't work if the window is not active.

[milos83]

8 hours ago, jdelaney said:

Use this instead:

WinMenuSelectItem

Sends generally don't work if the window is not active.

Thanks, but I don't need a workaround.

I'm just checking to see if this is a bug since ControlSend should never block execution.

[alienclone]

ControlSend is not blocking execution, your dummy gui is causing a problem, when i removed it from the script everything completed.

[milos83]

Just now, alienclone said:

ControlSend is not blocking execution, your dummy gui is causing a problem, when i removed it from the script everything completed.

Are you serious?

[alienclone]

2 minutes ago, milos83 said:

Are you serious?

usually

[milos83]

Just now, alienclone said:

usually

That code is showing how in certain condition the ControlSend is blocking further script execution.

You can't remove a part of code and say "Here! It doesn't block anymore!" XD

[alienclone]

add to see which line of code is hanging.

Opt("TrayIconDebug", 1) ;0=no info, 1=debug line info

 

[milos83]

4 minutes ago, alienclone said:

add to see which line of code is hanging.

Opt("TrayIconDebug", 1) ;0=no info, 1=debug line info

 

Can't be used because as soon as you give focus to anything else, the ControlSend finishes.

Simple ConsoleWrite is enough.

Here, run this, don't click anything and see for yourself

$gGUIDummy = GUICreate("")

Run("notepad.exe")

$HWND = WinWait("Untitled - Notepad")

WinActivate($gGUIDummy)

ConsoleWrite("Sending..." & @CRLF)
ControlSend($HWND, "", 0, "!f") ;control Id 0 is the issue here

 

[BrewManNH]

It is working for me, if you change the WinActivate line to the Notepad window instead of your invisible window. As previously stated, sometimes windows resist automation unless they're the active window.

[alienclone]

1 minute ago, milos83 said:

Can't be used because as soon as you give focus to anything else, the ControlSend finishes.

Simple ConsoleWrite is enough.

Here, run this, don't click anything and see for yourself

$gGUIDummy = GUICreate("")

Run("notepad.exe")

$HWND = WinWait("Untitled - Notepad")

WinActivate($gGUIDummy)

ConsoleWrite("Sending..." & @CRLF)
ControlSend($HWND, "", 0, "!f") ;control Id 0 is the issue here

 

this reproduced the error for me and you are correct, it is hanging at controlsend. did not realize that my act of changing focus was the reason the script was finishing for me.

[BrewManNH]

I tried this numerous times, it never hung for me.

[benners]

If it is the controlId that is the issue, try specifying the control

$gGUIDummy = GUICreate("")

Run("notepad.exe")

$HWND = WinWait("Untitled - Notepad")

WinActivate($gGUIDummy)

ConsoleWrite("Sending..." & @CRLF)
ControlSend($HWND, "", "[CLASS:Edit; INSTANCE:1]", "!f") ;control Id 0 is the issue here

There is also the issue of the characters you're sending. If your trying to drop down the file menu on notepad, it will have to be the active window to access the menu.

Edited January 17, 2018 by benners

[alienclone]

i think general help and support forum may only bring "do X to workaround".

maybe the development forum may have answers to WHY the command is hanging instead of exiting the script immediately and throwing the error code. 

[BrewManNH]

46 minutes ago, alienclone said:

may have answers to WHY the command is hanging instead of exiting the script immediately

I have never had this script hang ever, it immediately returns after the ControlSend command for me. Probably an issue on the computers being used.

[jdelaney]

I'm able to reproduce the hang, along with the window error tone.  Like I said though, it's because sends in Microsoft environments are flakey on inactive windows.  ControlSetText will work fine, WinMenuSelectItem will work fine, but Send and ControlSend will not.  This isn't anything to do with autoit...if you think it's a bug, create one at Microsoft.

Workaround 1:

$gGUIDummy = GUICreate("")
Run("notepad.exe")
$HWND = WinWait("Untitled - Notepad")
WinActivate($gGUIDummy)
ConsoleWrite("Sending..." & @CRLF)
;~ ControlSend($HWND, "", "", "!f") ;control Id 0 is the issue here
WinMenuSelectItem($hWnd,"","&File","&Save")
ConsoleWrite("sent..." & @CRLF)

Workaround 2:

$gGUIDummy = GUICreate("")
Run("notepad.exe")
$HWND = WinWait("Untitled - Notepad")
WinActivate($gGUIDummy)
ConsoleWrite("Sending..." & @CRLF)
;~ ControlSend($HWND, "", "", "!f") ;control Id 0 is the issue here
;~ WinMenuSelectItem($hWnd,"","&File","&Save")
Run(@AutoItExe & ' /AutoIt3ExecuteLine "ControlSend(Hwnd(' & $HWND & '), '''', '''', ''!f'')"')
ConsoleWrite("sent..." & @CRLF)

Then again, maybe I'm wrong, and this should be checked out by a developer here.  Interesting that initiating a new process to do the controlsend does not deadlock.

 

Scenario 1 (provided by original poster), ControlSend to open the file menu on an inactive window causes a windows 'error' tone, and the file menu does not open.  Script is deadlocked until user does some action (a mouse click, or a send)

Workaround 1: opens save menu as expected, no deadlock

Workaround 2: should have same results as Scenario 1, theoretically, but instead, there is no deadlock, no 'error' tone, and the File menu opens.

@Jos, can you enlighten us?

Edited January 18, 2018 by jdelaney

[milos83]

10 hours ago, jdelaney said:

Interesting that initiating a new process to do the controlsend does not deadlock.

That's another reason why I think that it is actually an autoit causing the problem.

ControlSend works fine on inactive windows.

Problem occurs specifically when my own created gui is in focus and I want to ControlSend another window.

Another test shoved that the Windows Error Tone is because ControlSend actually sent, but to the wrong window.

ControlSend($HWND, "", 0, "!f")

When third parameter is 0, ControlSend will be sent to currently active window.

Being that (in the example) the current active window is autoit gui without a menu, it creates the error sound.

 

Edited January 18, 2018 by milos83

[milos83]

bump

[Earthshine]

maybe you should file a bug in their system. I get the results you get btw

Edited January 22, 2018 by Earthshine

[Earthshine]

I just tested the workaround 1 that was posted above. I commented out the first line and added a declaration for the dummy. Works!!

;~ $gGUIDummy = GUICreate("")
Local $gGUIDummy
Run("notepad.exe")
$HWND = WinWait("Untitled - Notepad")
WinActivate($gGUIDummy)
ConsoleWrite("Sending..." & @CRLF)
;~ ControlSend($HWND, "", "", "!f") ;control Id 0 is the issue here
WinMenuSelectItem($hWnd,"","&File","&Save")
ConsoleWrite("sent..." & @CRLF)

I think as long as you use a valid dummy variable (not defined on the fly, EVER) it seems to work. no errors.

 

Edited January 22, 2018 by Earthshine