On Sat, 11 Mar 2000, Lars Thomas Denstad wrote:
> [snip]
> > I have created a program that, with the help of a GtkSocket, embedds a
> > window of another application into it. In this program, I
> > would like to be
> > able to show a menu, if the user clicks with some button and some
> > modifiers somwhere in the embedded window. It is an easy task
> > to set the
> > event mask for that window, but the Gtk main-loop will happily discard
> > that event, whilst it does not come from a widget, and is not
> > a property
> > delete event. How do I work around this, or is it something
> > I've overseen?
> [snip]
>
> This looks like multiple processes to me, do you/we really want to start
> with IPC just to give the plugin a graphical user interface?
Cannot be avoided, as any interaction with GUI toolkits from within
the same thread as the processing will cause RT problems.
> One of the goals should probably be to have the plugin and the
> plugin-frontend run in the same process-space?
No, because not all implementations *can* or *should* keep both
parts in the same process space. Running the processing in the kernel
(RTLinux) or on another machine rules any "direct access" plugin/GUI
interaction system out. Further, separating the processing from the
GUI improves reliability, as the system can be made to handle GUI
crashes without taking out the processing engine.
//David
.- M u C o S --------------------------------. .- David Olofson ------.
| A Free/Open Multimedia | | Audio Hacker |
| Plugin and Integration Standard | | Linux Advocate |
`------------> http://www.linuxdj.com/mucos -' | Open Source Advocate |
.- A u d i a l i t y ------------------------. | Singer |
| Rock Solid Low Latency Signal Processing | | Songwriter |
`---> http://www.angelfire.com/or/audiality -' `-> [EMAIL PROTECTED] -'
