Hi Owen,
On Thu, 2007-03-15 at 11:55 -0400, Owen Taylor wrote:
..
> For your purposes, you'd probably be better off modifying your patch
> so that the call to _gdk_events_init() was skipped, but that returns
> you to having a GDK with a number of things that don't quite work (not
> counting the big things that don't work like expose events!)
Clearly to do event management it's a much bigger step here, but would
it be acceptable to have a clearly documented (wrt. the extremely
limited use) API that would just allow the immediate gtk+ rendering code
to be used ? [ ie. almost a pure Qt theme-enabling API ;-].
> - To update XSettings ... if GTK+ doesn't get events, then it won't
> catch (among other things) theme changes
Presumably that could be done by injecting GDK_SETTING events into
gtk_main_do_event ?
> - To remove elements from the queue used for translation and
> anti-exposes. (it no longer grows without bounds, but there is
> some performance penalty for not trimming it)
I imagine in general expose events would be handled by the other
toolkit / controlling app, so perhaps the queue wouldn't be such a
problem ?
> - To know when windows are destroyed
No idea how Ricardo is handling that.
Anyhow - glad that the concept of a suitably limited functionality, X11
only API, is at least not unreasonable :-)
Thanks,
Michael.
--
[EMAIL PROTECTED] <><, Pseudo Engineer, itinerant idiot
_______________________________________________
gtk-devel-list mailing list
gtk-devel-list@gnome.org
http://mail.gnome.org/mailman/listinfo/gtk-devel-list
