On Sun, May 3, 2009 at 7:50 PM, Evan Martin <[email protected]> wrote: > Look at base/gfx/gtk_native_view_id_manager -- it implements #2 for GTK.
Interesting. That's similar to what I had in mind, but not quite as tight in the sense that it lets one renderer interact with view_ids from another renderer. For those of you that think better in code, what I had in mind is something like: http://codereview.chromium.org/100321 > It may be the case that none of those listed calls *should* need to > specify a window -- we know which renderer they're calling from so we > can map that back to the implicit current window. (Maybe you can get > window info from windows you've spawned, though...) There were some complications when I tried to do this for ScriptedPrint. I didn't quite understand why, but some folks were worried about deadlocks. (Although, they think the deadlocks will go away after some refactoring work that's underway.) Adam --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
