On Tue, 15 Jun 2010, Jeremy wrote:
I.e. the plugin provides both an internal and external UI, and the host
application picks which one. You can already do that.
I was under the impression that external UIs use some form of IPC to
communicate, while internal UIs use callbacks to the host.
Yes.
Otherwise, every host has to have a Qt-external-window
setup, an FLTK-external-window setup, a GTK-external-window
setup, etc. Kind of defeats the purpose of having the
external UI, doesn't it?
-gabriel
_______________________________________________
Linux-audio-dev mailing list
Linux-audio-dev@lists.linuxaudio.org
http://lists.linuxaudio.org/listinfo/linux-audio-dev
