[interfacekit] Why B_QUIT_REQUESTED in BApplication::DispatchMessage()?
- From: Ingo Weinhold <bonefish@xxxxxxxxxxxxxxx>
- To: Interface Kit <interfacekit@xxxxxxxxxxxxx>
- Date: Sat, 02 Jul 2005 19:14:29 +0200
Howdy,
currently implementing the application shutdown process I started
wondering, why we handle B_QUIT_REQUESTED in
BApplication::DispatchMessage() although it would be handled in
BLooper::DispatchMessage() almost the same. The only difference seems to be
that BLooper sends a helpful reply (including the QuitRequested() result
and the looper thread ID) when the message was sent synchronously.
In R5 it is done similarly, with the exception that the BApplication
version checks the B_QUIT_REQUESTED message for a boolean "_shutdown_"
field and sends a special message to the registrar, if it is present and
true.
Unless someone objects, I'll remove the B_QUIT_REQUESTED case in our
BApplication::DispatchMessage() and let BLooper also send a reply, if the
message contains a positive "_shutdown_" field.
CU, Ingo
Other related posts: