#6246: Invalid handling of intersected BViews. ---------------------------------+------------------------------------------ Reporter: X512 | Owner: axeld Type: enhancement | Status: closed Priority: normal | Milestone: R1 Component: Kits/Interface Kit | Version: R1/alpha2 Resolution: invalid | Keywords: Blockedby: | Patch: 0 Platform: All | Blocking: ---------------------------------+------------------------------------------ Comment(by X512): Replying to [comment:8 axeld]: > I wonder, what are the expected semantics? Which of the two views should be on top of the other? Always the latter? Views must be drawn in the same order, as it is stored in list. From BeBook: >AddChild() makes aView a child of the BView, provided that aView doesn't already have a parent. The new child is added to the BView's list of children immediately before the named sibling BView. If the sibling is NULL (as it is by default), aView isn't added in front of any other view—in other words, it's added to the end of the list. BeOS API actually support this feature, but it isn't implemented. -- Ticket URL: <http://dev.haiku-os.org/ticket/6246#comment:9> Haiku <http://dev.haiku-os.org> Haiku - the operating system.