On Wed, Jun 6, 2012 at 6:25 AM, Stephan Aßmus<superstippi@xxxxxx> wrote:
I am pretty sure I do this all the time. I have the suspicion that you are
simply dead-locking by trying to quit the settings window. Just don't do
anything, the BApplication will already take care to quit all child windows
that are still present when BApplication::Quit() runs.
Nope, if any window returns false from QuitRequested(), so will
BApplication::QuitRequested(), which will consequently cause the
registrar to cancel the shutdown process. Vision used to have a
similar problem years ago. I suppose you might be able to get around
that by overriding BApplication::QuitRequested() and explicitly
quitting that particular window without asking nicely though.
