[interfacekit] Re: Help understanding some BeOS concepts.

From: "Axel Dörfler" <axeld@xxxxxxxxxxxxxxxx>
> "Adi Oanca" <adioanca@xxxxxxxxxxxxx> wrote:
> >     The first "states" that the window should be the last to become
> > front-most( for > me = focus =
> > active). OK, I'll make all other windows(also the ones behind it) the
> > active ones, > until there
> > is no window that doesn't have B_AVOID_FRONT. Then I'll pass the
> > active state > to it.
> >     Is this OK?
>
> I don't think this is okay - although I haven't used it in real life
> yet, I think that B_AVOID_FRONT exactly does what its name entails: it
> will stay behind other windows whenever possible - I don't think that
> has anything to do with the activity/focus of that window.
> Please correct me if I'm wrong here :)

    Nope. It seems testing is on mine and DW's side.
    If you have lots of window open and lastly you open one with B_AVOID_FRONT, 
that one will
become the front-most(and receives keyboard events = focus). If then you 
activate another window
our window becomes the second. If then you close that first window, our window 
won't become the
most front-most one, but the ex-third will. So our window will be the second, 
again. This
process repeats until there is no window that could take focus before ours, and 
inevitably(being
the last one) it will become the front-most.

    OK, that is solved, what about the "subset" THING!?

PS: I think I elucidated the mystery behind B_AVOID_FOCUS, so leave that 
subject alone.


Adi.

Other related posts: