• 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: Properties displayed in UI
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Properties displayed in UI


  • Subject: Re: Properties displayed in UI
  • From: William Stewart <email@hidden>
  • Date: Fri, 15 Jun 2007 13:03:27 -0700


On 15/06/2007, at 11:30 AM, Bjorn Roche wrote:


On Jun 11, 2007, at 3:26 PM, William Stewart wrote:

We broke out the factory preset property from the Cocoa generic view (which AU Lab uses), and provide a means of handling the presets outside of the view. The preset menu is found in the carbon generic view (which you must be using). We are encouraging developers to move to the cocoa views, so if you can do that, you will see the same view as AU Lab displays.

I see what you are suggesting. It seems I need to do something like this:


if there is a non-generic carbon view:
	display it
else
	display cocoa view, whether generic or not

Unfortunately, I am stuck on the very first step: how do I distinguish carbon generic views from non-generic views? Does it have to do with the number of views associated with the kAudioUnitProperty_GetUIComponentList property? This appears to be undocumented.

In general an AU won't publish any components in its GUI list if it doesn't have custom views. Some of Apples' AUs do publish the carbon generic view (because it has some features that the host app generic views don't have).


In AULab if the AU publishes a carbon custom view, we'd also filter it, so that if it had a component fields of:

guiComponentFromAU.componentType *is* kAudioUnitCarbonViewComponentType;
guiComponentFromAU.componentSubType *is* kAUCarbonViewSubType_Generic;
guiComponentFromAU.componentManufacturer *is* kAudioUnitManufacturer_Apple;


we know it is the generic view and just use the cocoa one instead (same idea as what you are doing below)

Bill


FWIW, I can easily see how to distinguish between generic and non- generic cocoa views, so my logic right now is more like this:


if there is a non-generic cocoa view:
	display it
else
	display carbon view, whether generic or not

	bjorn

-----------------------------
Bjorn Roche
XO Wave
Digital Audio Production and Post-Production Software
http://www.xowave.com
http://blog.bjornroche.com
http://myspace.com/xowave



--
mailto:email@hidden
tel: +1 408 974 4056
________________________________________________________________________ __
"Much human ingenuity has gone into finding the ultimate Before.
The current state of knowledge can be summarized thus:
In the beginning, there was nothing, which exploded" - Terry Pratchett
________________________________________________________________________ __


_______________________________________________
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


References: 
 >Properties displayed in UI (From: Bjorn Roche <email@hidden>)
 >Re: Properties displayed in UI (From: William Stewart <email@hidden>)
 >Re: Properties displayed in UI (From: Bjorn Roche <email@hidden>)

  • Prev by Date: Re: how to make kAudioUnitProperty_BusCount writable
  • Next by Date: HRTF Spatialization in Core Audio
  • Previous by thread: Re: Properties displayed in UI
  • Next by thread: nxm effect
  • Index(es):
    • Date
    • Thread