From b9563a6fd991b5b63a808fccb7f90ef9cbdc0509 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Stephan=20A=C3=9Fmus?= Date: Tue, 23 Jun 2009 12:20:14 +0000 Subject: [PATCH] Added NOTE on how to handle QuitRequested in the application and why using the base class version is fine for now. git-svn-id: file:///srv/svn/repos/haiku/haiku/trunk@31202 a95241bf-73f2-0310-859d-f6bbb57e9c96 --- src/apps/debugger/Debugger.cpp | 11 ++++++++++- 1 file changed, 10 insertions(+), 1 deletion(-) diff --git a/src/apps/debugger/Debugger.cpp b/src/apps/debugger/Debugger.cpp index 8eb9332218..8bb5ffb653 100644 --- a/src/apps/debugger/Debugger.cpp +++ b/src/apps/debugger/Debugger.cpp @@ -271,7 +271,16 @@ printf("debugger for team %ld created and initialized successfully!\n", team); { // TODO:... // return true; -return BApplication::QuitRequested(); + // NOTE: The default implementation will just ask all windows' + // QuitRequested() hooks. This in turn will ask the TeamWindows. + // For now, this is what we want. If we have more windows later, + // like the global TeamsWindow, then we want to just ask the + // TeamDebuggers, the TeamsWindow should of course not go away already + // if one or more TeamDebuggers want to stay later. There are multiple + // ways how to do this. For examaple, TeamDebugger could get a + // QuitReqested() hook or the TeamsWindow and other global windows + // could always return false in their QuitRequested(). + return BApplication::QuitRequested(); } private: