Re: Using bindings in AU Cocoa GUI?
Re: Using bindings in AU Cocoa GUI?
- Subject: Re: Using bindings in AU Cocoa GUI?
- From: Per Bull Holmen <email@hidden>
- Date: Thu, 23 Feb 2012 16:23:37 +0100
Den 14:50 23. februar 2012 skrev Paul Davis
<email@hidden> følgende:
> On Wed, Feb 22, 2012 at 11:36 AM, Per Bull Holmen <email@hidden> wrote:
>> Hi
>>
>> Cocoa developers who make complex GUIs are very spoilt with the use of
>> bindings. They can make it a breeze to program complex interactions
>> between the different controls and the model objects. I was wondering,
>> is there something technical prohibiting you from using bindings in a
>> Cocoa AU GUI? Things like performance/stability? I know that you'd
>> have to still maintain the separation of address space etc., the
>> normal requirements for an AU GUI.
>
> keep in mind that the host owns the NSWindow in which your view will
> reside, and may choose to handle events in a way that prevents your
> controller from ever seeing them.
Thanks. I hadn't thought about that. I don't know how the standard
Cocoa controller mechanism works below the surface, I have been
dealing mostly with the old target/action paradigm in Cocoa apps. Also
I have next to no experience with AudioUnits. But at least the old
target/action paradigm must surely work for an AudioUnit? Otherwise it
could easily turn into spaghetti, I'd think, if all GUI logic is
implemeted in the NSView itself? Hmmm....
I suppose most plugin developers don't care about the cocoa controls
like NSButton, NSSlider etc, cause they develop cross-platform. But
for MacOS X developers they might be appropriate, since they can later
be customized with custom drawing code.
Per
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Coreaudio-api mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden