[openbeos] Re: BWindow->AddChild(view, sibling!=NULL) bug

Thanks Axel.  As usual, you are incredibly quick to answer even the most
obscure question.  You are a real treasure in the BeOS community :)

Your suggestion did work, though I'm still curious as to why the original
BWindow version of AddChild(control, background) would not work correctly
when I actually specify insert before sibling.  Following the description in
the BeBook, messages are passed from highest child to lowest (until its
accepted), and if the control view is higher than background (what ChildAt()
confirms), then control_view should have recieved the message first.


I was curious as to why the internal handler list order did not match the
child order.


Cheers.



On 8/8/06, Axel Dörfler <axeld@xxxxxxxxxxxxxxxx> wrote: 

"Zenja Solaja" <solaja@xxxxxxxxx> wrote:
> a) Is this a BeOS bug, or am I wrong?

What you want is done like this:

AddChild(background);
background->AddChild(control);

while you can have sibling views, BeOS does not support a defined
behaviour in case they overlap - and it's the same with Haiku. It's not
a bug, it's a documented property.

Bye,
   Axel.



Other related posts: