Le 10/11/2010 13:55, Alan Bateman a écrit :
Rémi Forax wrote:
The soft way to kill a process on windows to send a WM_CLOSE/WM_QUIT.
http://stackoverflow.com/questions/2055753/how-to-gracefully-terminate-a-process
Rémi
Yes, that could work for graphical/foreground applications but there
is also
The soft way to kill a process on windows to send a WM_CLOSE/WM_QUIT.
http://stackoverflow.com/questions/2055753/how-to-gracefully-terminate-a-process
Rémi
Le 10/11/2010 10:46, Andreas Kohn a écrit :
On Wed, 2010-11-10 at 06:02 +1000, David Holmes wrote:
Hi Andreas,
On 10/11/2010 5:31 AM
Rémi Forax wrote:
The soft way to kill a process on windows to send a WM_CLOSE/WM_QUIT.
http://stackoverflow.com/questions/2055753/how-to-gracefully-terminate-a-process
Rémi
Yes, that could work for graphical/foreground applications but there is
also the issue of services or applications that d
On 11/10/2010 1:48 PM, Rémi Forax wrote:
The soft way to kill a process on windows to send a WM_CLOSE/WM_QUIT.
http://stackoverflow.com/questions/2055753/how-to-gracefully-terminate-a-process
This only works for GUI applications that process window messages (e.g.
AWT or Swing apps). If an appl
On Wed, 2010-11-10 at 06:02 +1000, David Holmes wrote:
> Hi Andreas,
>
> On 10/11/2010 5:31 AM, Andreas Kohn wrote:
> > there seems to be a difference in behavior between Process#destroy()
> > implementations on Windows and !Windows: on Windows TerminateProcess()
> > [1] is called, which gives the
Hi Andreas,
On 10/11/2010 5:31 AM, Andreas Kohn wrote:
there seems to be a difference in behavior between Process#destroy()
implementations on Windows and !Windows: on Windows TerminateProcess()
[1] is called, which gives the process no way to react or in any way
intercept the termination, while
