[interfacekit] Re: Why B_QUIT_REQUESTED in BApplication::DispatchMessage()?

["Axel Dörfler" <axeld@xxxxxxxxxxxxxxxx>]

Ingo Weinhold <bonefish@xxxxxxxxxxxxxxx> wrote:
> 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.

Sure, go ahead, I can't imagine that to cause any problems. In fact, I 
think that your version is much cleaner and more correct.

Bye,
   Axel.

• References:
  • [interfacekit] Why B_QUIT_REQUESTED in BApplication::DispatchMessage()?
    • From: Ingo Weinhold

Other related posts:

[interfacekit] Why B_QUIT_REQUESTED in BApplication::DispatchMessage()?

[interfacekit] Re: Why B_QUIT_REQUESTED in BApplication::DispatchMessage()?