Re: Emacs does not listen on w32

[Lennart Borgman (gmail)]

Lennart Borgman (gmail) wrote:
> David Kastrup wrote:
> > "Lennart Borgman (gmail)" <address@hidden> writes:
> >
> > > Juanma Barranquero wrote:
> > > > On Sun, Apr 13, 2008 at 11:04 PM, Lennart Borgman (gmail)
> > > > <address@hidden> wrote:
> > > >
> > > > >  By recognizing that it has recieved WM_CLOSE. I tried to say that 
> > > > > this
> > > > > should be handled as a kind of "quit" in those cases.
> > > > Why should clicking into the [X] box interrupt useful work without
> > > > asking?
> > > It is the user that is clicking the [X]. Maybe there should be a
> > > question if the the ongoing work should be interrupted though.
> >
> > If I have two frames, and start some calc command in one frame, then
> > click [X] on another frame, I don't want the calculation to stop.  If
> > Emacs can't close the frame "out of processing order" then I'll just
> > have to wait for the calculation to finish, or stop it manually.
>
> But if you have two frames and click [X] then Emacs does not want to 
> exit so this problem should not occur then. (There will be no WM_CLOSE.)

Eh, that was wrong. I have forgotten how it work, I thought there was a 
special message for exiting. But if I am right now sending WM_CLOSE to 
the last window/frame means "exit application" in w32 message language.

BTW, I just saw that there is an API IsHungAppWindow that considers the 
application hung if it has not called PeedMessage the last 5 seconds.