>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.
 
On Tue, Jun 15, 2010 at 2:14 PM, Paul Davis <paul@linuxaudiosystems.com> wrote:
On Tue, Jun 15, 2010 at 12:30 PM, Jeremy <jeremybubs@gmail.com> wrote:

> How about this idea?  The plugin is responsible for creating its own window
> if the host doesn't know how to do it.

insufficient, and already more or less assumed by any sane API. but
the issue isn't window creation. its event dispatch.

Do you mean passing resizing and clicking events and such, or like updates to the input controls?

Jeremy