F
fdmaxey
I am currently using one process to find if another MDI windows process
is running. If it is SendMessage is used to display a given screen.
I use GetProcessesByName to determine if the target windows process was
running. If not, it is started.
Once the target process started, the MainWindowHandle is retrieved and
used by SendMessage to direct the target process to display a given
screen.
All well and good. As of late however, we seem to be running into
problems because GetProcessesByName is taking prohibitive amounts of
time and even returning an error.
SystemManager can be employed to get the process data much faster and
more reliably, but it doesn't include the main window handle.
Is there any way that I can determine the main window handle of the
target process by any other method than GetProcessesByName?
Frank Maxey
is running. If it is SendMessage is used to display a given screen.
I use GetProcessesByName to determine if the target windows process was
running. If not, it is started.
Once the target process started, the MainWindowHandle is retrieved and
used by SendMessage to direct the target process to display a given
screen.
All well and good. As of late however, we seem to be running into
problems because GetProcessesByName is taking prohibitive amounts of
time and even returning an error.
SystemManager can be employed to get the process data much faster and
more reliably, but it doesn't include the main window handle.
Is there any way that I can determine the main window handle of the
target process by any other method than GetProcessesByName?
Frank Maxey