All this would be a lot simpler if the common GUI
toolkits would provide
a call that would allow one to create a raw X window that wil be
connected to their internals and that gets its raw X events delivered
to a user specified callback. From there on, the toolkit or library used
by the plugin takes over. That's really all that's needed.
i've been talking about this a lot on the GMPI lists as
well. yes, thats pretty much exactly what is needed. how can it be so
hard for these people to understand that they cannot always control
or own the event loop?
Well, we COULD discuss this with the QT/GTK folk. However, I personally