Well that MIGHT be because you have a "quit" command in the Close
handler of another window. So this would happen:
1) User selects Quit. App tries to close all windows.
2) One window fires a second "quit" command from the "Close" handler
3) Another window refuses to close (ie. returns True from CancelClose)
4) The (first) quit command is cancelled because of the no-close window.
5) The app starts to process the second "quit" command.
6) Repeat and fade...
Cheers,
Frank+++
Dominik Fusina - The Captain wrote:
>
> on 27/02/02 17:36, Dominik Fusina - The Captain at captain at nemo dot fr
> wrote:
>
> > During my tests, I found a strange comportment from the window event
> > "CANCELCLOSE".
> >
> >
> > If you return "false", the event passes to CLOSE. I understand, no problem.
> > But if you return "true", the CANCELCLOSE is called twice, and CLOSE is not
> > called (correct).
> >
> > Why CANCELCLOSE is called twice ???
> > Is it a bug ?
> > What is the explanation ?
> > Perhaps in the list, someone knows the reason...
> >
> >
> > Thanx.
>
> OUPS! I forget something...
> Big precision: that problem occurs only when you call "QUIT" (Apple+Q).
>
> Dominik Fusina
> Captain of NEMO
--
Günter Schmidt & Co. oHG
Frank Bitterlich eMail: bitterlich at gsco dot de
Schlosserstr. 2-4 WWW: http://www.gsco.de/gsco
D-60322 Frankfurt Tel.: 069 / 156809-29
GERMANY Fax: 069 / 156809-28
|