• 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: Property notification questions
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Property notification questions


  • Subject: Re: Property notification questions
  • From: Bill Stewart <email@hidden>
  • Date: Wed, 12 Feb 2003 17:59:18 -0800

It just tells the notification service that there will be a potential parameter change to take care of next time round... It doesn't issue the notification or do any other significant work at all

Bill

On Wednesday, February 12, 2003, at 04:32 PM, Chris Reed wrote:


On Wednesday, Feb 12, 2003, at 16:19 US/Central, Bill Stewart wrote:

I'd actually use the AUParameterListener to do this communication...

Create a bunch of private parameters that aren't going to be registered or have values in the scope objects...

Then, as you need to get this information use the parameter listener API to issue a notification of a parameter value change... (make sure you actually change the value of the param - just do a ++ for instance so that the param listener will actually register a change in the value of the parameter...

Thus - you have a displayNoteOnFeedbackParam
in your au:
mDisplayNoteOnFeedbackParamValue++;
AUParameterListenerNotify(NULL, NULL, myFeedbackParamStruct);

Then your view registers for notifications for changes to that parameter value and sets the run loop that it wants to get notification on (including the granularity) - so then your view will see the notification on its UI thread...

Then - when your view gets this notification it know what it has to do (ie. query the value of the property for instance) in response to that...


Oh, cool. I hadn't really thought about using the parameter listeners to do this for me.

One question, though... Is calling AUParameterListenerNotify() nonblocking? I don't see how it can be if it installs a CFRunLoopTimer on the main run loop.

-chris


-- 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
________________________________________________________________________ __
_______________________________________________
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.
  • Follow-Ups:
    • Re: Property notification questions
      • From: Chris Reed <email@hidden>
References: 
 >Re: Property notification questions (From: Chris Reed <email@hidden>)

  • Prev by Date: Re: How are AU User Presets handled?
  • Next by Date: Re: Property notification questions
  • Previous by thread: Re: Property notification questions
  • Next by thread: Re: Property notification questions
  • Index(es):
    • Date
    • Thread