Re: Run Loops and CFMessagePorts
Re: Run Loops and CFMessagePorts
- Subject: Re: Run Loops and CFMessagePorts
- From: William Stewart <email@hidden>
- Date: Tue, 28 Feb 2006 12:10:37 -0800
On 28/02/2006, at 9:49 AM, Wayne Anderson wrote:
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.
Is this in the context of an application or an AudioUnit?
Bil
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
--
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