• 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: auval problem
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: auval problem


  • Subject: Re: auval problem
  • From: tahome izwah <email@hidden>
  • Date: Mon, 15 Jun 2009 09:07:14 +0200

Thank you!

Is there a list of keys and values that are mandatory for a plug in to
work? I cannot call the base classes' SaveState to create the plist
info for me (I have a good reason for this) and need to construct the
plist from scratch.

Thanks!
--th


2009/6/12 William Stewart <email@hidden>:
> CFShow(theClassData)
>
> if you look in AUBase::SaveState you'll see that there are a collection of
> keys added there to identify which AU the class data comes from - seems like
> you are misssing a key
>
> Bill
>
> On Jun 11, 2009, at 8:24 PM, tahome izwah wrote:
>
 _______________________________________________
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

  • Follow-Ups:
    • Re: auval problem
      • From: tahome izwah <email@hidden>
References: 
 >auval problem (From: tahome izwah <email@hidden>)
 >Re: auval problem (From: William Stewart <email@hidden>)

  • Prev by Date: Audio Units MIDI output
  • Next by Date: Re: Audio Units MIDI output
  • Previous by thread: Re: auval problem
  • Next by thread: Re: auval problem
  • Index(es):
    • Date
    • Thread