window identification / fixing current window

[_alexei@…]

Currently, AutoIt can not guarantee keystrokes sent by Send would go to the particular window. Focus may change because of many reasons (other app. activity, system popup, user interference, etc.)
There is no simple way to find a window with particular relation to already known window in terms of child/parent/sibling/owner of any level, also, verifying window class and other properties. That's pretty easy to implement by verifying each window in Z-chain against specified properties and relations. I want to be 100% sure AutoIt clicks the button (or sends keystrokes to the window) it was programmed to.
Bottom line: util window identification becomes reliable, AutoIT is just a dangerous toy, unsuitable to serious applications.
BTW, "special treatment" of controls creates unnecessary limitations, as controls are just windows with specific relations to the parent/owner.

[TicketCleanup]

Automatic ticket cleanup.

[Valik]

Replying to _alexei@sbcglobal.net:

Currently, AutoIt can not guarantee keystrokes sent by Send would go to the particular window. Focus may change because of many reasons (other app. activity, system popup, user interference, etc.)

What's your point? This is true if you're are sending keystrokes via your keyboard as well.

There is no simple way to find a window with particular relation to already known window in terms of child/parent/sibling/owner of any level, also, verifying window class and other properties. That's pretty easy to implement by verifying each window in Z-chain against specified properties and relations.

There certainly is. The Windows API function GetWindow(), which allows traversal of the Z-Order is exposed by the UDF _WinAPI_GetWindow().

I want to be 100% sure AutoIt clicks the button (or sends keystrokes to the window) it was programmed to.

Then you ControlSend(), ControlClick() or ControlCommand(). You can't expect something that's "global" like Send() or MouseClick() to work any better than human interaction because it suffers from the same pitfalls.

Bottom line: util window identification becomes reliable, AutoIT is just a dangerous toy, unsuitable to serious applications.

You do not know what you are talking about. Your statement is needlessly inflammatory because of your own incompetence. Window identification is reliable, it's just apparent you can't be bothered to learn how to use the language properly to facilitate that.

BTW, "special treatment" of controls creates unnecessary limitations, as controls are just windows with specific relations to the parent/owner.

And what are these limitations you don't mention? It's trivial to obtain the HWND of a control and pass it to any AutoIt function expecting an HWND, or to anything else expecting an HWND. The fact is, treating controls as special is just syntactic convenience for a special parent/child relationship. But it is not a limitation, you have the option to obtain the HWND and use whatever function you like on that HWND. Once again, I think you are criticizing the language yet you are a long way from actually knowing how to use it.

This has been a waste of my time and your time. You haven't suggested a feature here. You've just went on a mini-rant out of your own ignorance of the language. I'm resolving this as Rejected.