AutoHotkey Community

I suggest that the documentation mention that opening a DOS Windows does not generate a processID under Windows XP and AutoHotKey.

Also, there are no examples of the commands using processID as the way of identifying a Window. I suggest that there be examples of the most complex use of each command, rather than just the simplest.

It's possible that I could help with documentation. There are numerous areas that need small improvements.

I'd welcome it. Feel free to contact me at support@autohotkey.com

I'm not sure what you mean by this. The following code on Windows XP does display the correct process ID for the launched console window:

... or did I misunderstand what you mean by "DOS Window"?

Jacques.

This command does not return a process ID:

Run DOS_Window.lnk,, Max, ProcessID

It is necessary to start command-line windows (DOS windows) with a shortcut, because starting any other way does not allow full control over the resulting window.

It's necessary to have the process ID because that is the only way to identify the DOS window reliably after it is opened.

Any answer to this?

(I'm very thankful for AutoHotKey.)

That's a tough one. I've also had trouble in the past getting cmd.exe windows to look exactly the way I want without resorting to a shortcut (.lnk file). But since Run can't get the PID of a launched shortcut, that leaves only WinGet or Process (or perhaps DllCall) as options to get the PID, which you implied are insufficiently accurate in this case.

The key HKEY_CURRENT_USER\Console (default console settings) and its subkeys (individual settings for CMD windows that open with speciic titles) can be used to fully control the appearance and behavior of CMD windows without resorting to shortcuts.

Jacques.

I think that will be useful. Thanks.

Great tip. Thanks Jacques .

This open source software provides completely controllable CLI (Command Line Interface) windows.

http://sourceforge.net/projects/console/

However, my guess is that it does NOT provide a Program ID (PID), because the program spawns a CLI (DOS) window after reading the configuration file.