• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: AU CreateUI
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: AU CreateUI


  • Subject: Re: AU CreateUI
  • From: Urs Heckmann <email@hidden>
  • Date: Thu, 21 Aug 2003 18:26:30 +0200

Am Donnerstag, 21.08.03, um 17:37 Uhr (Europe/Berlin) schrieb Robert Fehse:

hi list

i have problems with the gui in au.
in CreateUI i want to have a pointer to my main plugin class(or another class
known by my plugin).
can i get it somehow ?

define your own properties for dsp<->view communication...

here's some sample code:

http://www.mat.ucsb.edu:8000


how is my gui constructed by host ?
is the class constructed every time the gui is opened or just a call to
CreateUI ?

some hosts will open/destroy the gui each time its needed/clicked away, some hosts will just hide the window...

Shouldn't make any difference for your gui...

is there another AU documentation then the standart one?
i'am looking for class hierarchy, calling orders and so on.

Well, once you get the concept behind the concept, that shouldn't be needed anymore. - The Apple provided base classes just do that for you... - they wrap the system calls (AudioUnit framework) to C++, capture the common cases, just to conveniently meet that stuff...

(In fact, there's not really a class hierarchy... However, you can use doxygen (www.doxygen.org) to create nice looking interactive documentation of the base classes.)

Commonly, if a host tries to do something in an order you don't like, you return an error. - For instance, if it sets a preset and your plug needs to be initialized before that, you'd return a NotInitialized error if it isn't...

at the moment it seems to me that the gui class is seperated from the plugin
and is just able to pass parameter values via AudioUnitGetParameter. am i
right ?

yes and no.

They are seperate components, but your communication isn't limitted to parameters.

You can pass direct pointers via properties, but there's no consensus here if that is valid or not, at least I think we agreed that it isn't good style 8-)

Hope this helps + Viele Gr|sse,

;) Urs
_______________________________________________
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.

References: 
 >AU CreateUI (From: "Robert Fehse" <email@hidden>)

  • Prev by Date: AU CreateUI
  • Next by Date: Cocoa views for AU
  • Previous by thread: AU CreateUI
  • Next by thread: Will this help?
  • Index(es):
    • Date
    • Thread