linuxaudio.org

--0016363b9bf898c0d7048916e937

Content-Type: text/plain; charset=ISO-8859-1
>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 wrote:
> On Tue, Jun 15, 2010 at 12:30 PM, Jeremy  wrote:

quoted text
>

> > 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
--0016363b9bf898c0d7048916e937

Content-Type: text/html; charset=ISO-8859-1

Content-Transfer-Encoding: quoted-printable
>I.e. the plugin provides both an internal and external UI, and the host=

 application picks which one. =A0You can already do that.I was unde=

r the impression that external UIs use some form of IPC to communicate, whi=

le internal UIs use callbacks to the host.
=A0On Tue, Jun 15, 2010 at 2:14 PM, Paul Dav=

is <paul=

@linuxaudiosystems.com> wrote:
On Tue, Jun 15, 2010 at 12:30 PM, Jeremy <jeremybubs@gmail.com> wrote:
> How about this idea? =A0The plugin is responsible for creating its own=

 window

quoted text
> 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
--0016363b9bf898c0d7048916e937--