[haiku-commits] Re: r33474 - haiku/trunk/src/apps/haiku3d
- From: "Axel Dörfler" <axeld@xxxxxxxxxxxxxxxx>
- To: haiku-commits@xxxxxxxxxxxxx
- Date: Wed, 07 Oct 2009 11:58:45 +0200 CEST
Ingo Weinhold <ingo_weinhold@xxxxxx> wrote:
> On 2009-10-07 at 09:29:55 [+0800], Rene Gollent <anevilyak@xxxxxxxxx>
> wrote:
> > On Tue, Oct 6, 2009 at 7:12 PM, <alex@xxxxxxxxxxxx> wrote:
> > > Log:
> > > * Fixed closing via deskbar's close all. The problem was that i
> > > forgot to
> > > define the app_flags in the rdef, case that isn't well handled
> > > apparently
> > > when creating a BMessenger targeting the app.
> > > Thanks to Michael and Rene for helping! Fixes #4712
> > Tracked this down: If no app flags are found in the app's
> > resources,
> > the default B_REG_DEFAULT_APP_FLAGS is used, which contains
> > B_ARGV_ONLY. BMessenger will refuse to construct a valid messenger
> > for
> > any app which has that in its flags, with the end result that
> > sending
> > messages to such an app is impossible. Is this deliberate, or an
> > oversight somewhere?
> If it's working the same way under BeOS, then this is deliberate. :-)
> I'm
> pretty sure B_ARGV_ONLY works the same. Not quite sure whether it is
> supposed to be a default flag, though.
Since CLI apps usually miss the flags, I would guess it is. However,
does it really make sense to prevent creating a messenger for them? If
it doesn't want to be queried, it won't answer anyway.
Bye,
Axel.
Other related posts:
