Window Bug

[tanaynigam12@…]

Hi Team,

I have an issue with a specific window that pops up during an installation. The error message window "Allscripts Pro EHR Client - InstallShield Wizard" does not close regardless of any implementation of AutoIT script tested on it. While the mouse clicks work manually or either of "Enter" or "Escape" work using the keyboard, they fail to close the window when implemented using the AutoIt script.

The scripts work perfectly fine throughout the implementation, which includes closing other windows and regular mouse clicks in any other window except this specific window.

On an attempt to debug the script, it appears that WinWait and WinActivate do return the Window Handle suggesting that the script detects the window. Moreover, any of the implementations of WinClose, ControlClick, MouseClick, and WinKill return value 1 indicating success. However, these do not close the window in any form.

Best Regards,
Tanay Nigam

[BrewManNH]

This is a question that you need to ask in the forum first, as there's no bug reported, and no script that demonstrates a bug posted.
Closing this.

[anonymous]

Hi BrewManNH,

Thanks for the response. The AutoIt tool is unable to perform any function on this specific window for no apparent reason. Having detected the window and return the Window handler using WinWait and WinActive, it appears that the tool reads the Window and all the variables related to the window including the 'OK' button.

Having tried WinClose, MouseClicks, ControlClick and any other related function on the Window, we found that it wasn't executing any of the functions that it normally does(We have executed the same function on numerous other Windows of the application successfully). Even MouseClick function seems absolutely unresponsive which has never happened. Moreover, these functions return the value 'successful' making the bug more absurd.

Given the state of the issue, it can only be concluded as an AutoIt bug since nobody is able to reason out the inconsistency in the execution.

[Melba23]

Quote/

Having tried WinClose, MouseClicks, ControlClick and any other related function on the Window, we found that it wasn't executing any of the functions that it normally does(We have executed the same function on numerous other Windows of the application successfully

/Quote

So how do you come to the conclusion that it is an AutoIt bug? If AutoIt interacts with other windows then the AutoIt code is certainly working - it must be something to do with this particular window which prevents AutoIt interaction. This is not uncommon with some apps (particularly games) - perhaps this is another case. Have you contacted the app developers to see if there is any reason why this "error" window (perhaps a hint in the type of dialog?) does not accept script interaction?

M23