• 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
Run Loops and CFMessagePorts
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Run Loops and CFMessagePorts


  • Subject: Run Loops and CFMessagePorts
  • From: Wayne Anderson <email@hidden>
  • Date: Tue, 28 Feb 2006 10:49:18 -0700

Hi All,

Sorry for the duplicate question, but I thought I would post this under its own topic.

What is the preferred way to get a signal into the main thread run loop from another thread within an application?
Say for example, I want to use the time stamp from the CA render thread and signal the app thread to update some widget.


From the discussion under another subject line (interapplication midi communication, cfmessageports, ques) it looks like using
CFMessagePorts could cause priority inversion problems because it allocates memory to send a message.



Any suggestions or additional insight on this question would be greatly appreciated.



Wayne


__________________________________ Wayne Anderson Red Rock Software, Inc.

_______________________________________________
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: Run Loops and CFMessagePorts
      • From: Doug Wyatt <email@hidden>
    • Re: Run Loops and CFMessagePorts
      • From: William Stewart <email@hidden>
  • Prev by Date: Re: Recognizing iSight as audio input device?
  • Next by Date: RE: Re: Recognizing iSight as audio input device?
  • Previous by thread: Re: MusicSequence CAShow statement and beats
  • Next by thread: Re: Run Loops and CFMessagePorts
  • Index(es):
    • Date
    • Thread