Re: AU interface consistency
Re: AU interface consistency
- Subject: Re: AU interface consistency
- From: Jim Wintermyre <email@hidden>
- Date: Tue, 1 Oct 2002 21:54:35 -0700
on 1/10/02 10:32 AM, Chris Reed wrote:
I'd also like to point out that since the AU edit views are HIView
objects, they can be embedded in a window you own instead of having to
be in their own window. Unless I am mistaken, VST custom edit views are
always shown in their own window (perhaps that's the only way I've ever
seen it--I am not all that familiar with the VST API). I think this is
an important distinction, because it gives the host app a little more
control over edit view, even if it looks radically different than the
rest of the app's UI.
Yes indeed - that was one of the reasons we defined the API for the view
component as we did (and why AudioUnitHosting was written the way it was) -
to reinforce the fact that you don't "have" to have a separate window for
every units UI...
It is actually possible for a VST host to present custom VST plug
UI's without opening a separate window. An earlier version of the
Spark FXMachine plugin (a VST plugin which is also a VST host) did
just that. It was cool because you could have multiple VST
"sub-plugs" loaded in the main Spark plug, and you could switch to
different plug UI's without opening multiple windows. I think they
had to play some games with the port though... or at least I did in
order to get my plugs to work properly inside their host. Anyway
this is probably a moot point now.
Jim
_______________________________________________
coreaudio-api mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/coreaudio-api
Do not post admin requests to the list. They will be ignored.