On Tue, 15 Jun 2010, Jeremy wrote:
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?
wait, isn't the
LV2UI_Descriptor->port_event() and LV2UI_Write_Function() interface toolkit
agnostic? Wouldn't it be possible to have toolkit agnostic host-facilitated
communication?
Yes, these are. And these allow plugins to communicate
with other plugins.
However, these functions are executed in the host
application's memory space. So, I don't see how it would
help in having FLTK widgets hosted by a Qt application.
-gabriel
_______________________________________________
Linux-audio-dev mailing list
[email protected]
http://lists.linuxaudio.org/listinfo/linux-audio-dev
