On Fri, 14 Oct 2005 08:38:49 -0700, "David Schnepper"
<[EMAIL PROTECTED]> wrote:
>The Windows notion of a "Console" is independent from a "visual window
>on the display". You can still have a Console without anything appearing
>on the screen. Generally, if you start a process from a cmd.exe
>w
Mark Hammond wrote:
>Sadly, I think GenerateConsoleCtrlEvent will not work for you. In
short, it
>is nearly useless :) The description of the function says it "sends a
>specified signal to a console process group that shares the console
>associated with the calling process" and it means it liter
Mark Hammond wrote:
>Sadly, I think GenerateConsoleCtrlEvent will not work for you. In short, it
>is nearly useless :) The description of the function says it "sends a
>specified signal to a console process group that shares the console
>associated with the calling process" and it means it litera
> I've looked around, but I wasn't able to find anything about this
> issue. I am writing an application that calls a separate windows
> application as a process. That's not a problem, I can get it to run and
> do what it needs to do. However, the normal way to stop the separate
> windows applic
At Thursday 13/10/2005 17:33, you wrote:
I've looked around, but I wasn't able to find anything about this
>issue. I am writing an application that calls a separate windows
>application as a process. That's not a problem, I can get it to run and
>do what it needs to do. However, the normal way
Hi all,
I've looked around, but I wasn't able to find anything about this
issue. I am writing an application that calls a separate windows
application as a process. That's not a problem, I can get it to run and
do what it needs to do. However, the normal way to stop the separate
windows app
