ok, cool... Thanks Peter... I thought the resizer needed to be a leaf in the view hierarchy to be drawn on top of all the other views and receive the mouse events...
So now I guess there is a way for the browser view to specify that this child has to be laid on top of the other child, right? Is it just by the order they are added as children of a parent, or is there another trick? Thanks again... BYE MAD On 12/13/08, Peter Kasting <pkast...@google.com> wrote: > On Fri, Dec 12, 2008 at 9:14 PM, Marc-Andre Decoste <m...@google.com> wrote: > >> So I'll try to make the resizer object a TabContents object, > > > This will be disaster, do not go this route. (TabContents means the > contents are a tab, i.e. a web page or one of our sson-to-be-disappearing > native views. This is not the case for your resizer.) > > You should probably just be a child of the main browser window, not of the > content area. This will make life much better when you're blending against > things like the download shelf, which themselves are going to be owned by > the browser window and not the content area. > > Ben is the right person to ask about this stuff. > > PK > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Chromium-dev" group. To post to this group, send email to chromium-dev@googlegroups.com To unsubscribe from this group, send email to chromium-dev+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/chromium-dev?hl=en -~----------~----~----~----~------~----~------~--~---
