On Tue, Feb 10, 2009 at 12:30 PM, Dean McNamee <[email protected]> wrote: > Evan just explained the xshape stuff to me today. I'm curious how > well it will work. You don't get alpha, etc. I could see it not > working out that well, but I guess it's up to how you divide it. > > I honestly don't think hit testing a 20 pixel high rectangular area is > going to be too tricky. Also, even with the button approach, even if > the window has areas that are see through, I'm not sure how the works > with events. I wouldn't be surprised if we'll have to do more > calculations when the button is pressed, to make sure it's not in the > space in between, etc. >
We'd use gdk_window_input_shape_combine_region, set up to match the exact (very close) region of the tab, which is not rectangular. If you do treat it as a rectangle, then you have to deal with clicking in the small space between the tabs. > I guess that means I support 2, along with reusing the animation classes, etc. > If majority opinion wants this, I will certainly go along with. I'd really like to hear some pros for 2 though. I don't see the advantages over 3. --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
