Re: CoreMIDI CFRunloop Question
Re: CoreMIDI CFRunloop Question
- Subject: Re: CoreMIDI CFRunloop Question
- From: Pete Gontier <email@hidden>
- Date: Thu, 12 Jun 2003 11:28:00 -0700
In a typical Carbon app, you shouldn't need to worry about run loops or
making explicit reference to threads. The purpose of the run loop usage
in the samples appears to be simply a way to make the process sit
around waiting for inputs in a friendly way (blocking) and without
incurring a lot of overhead (by pulling in Carbon). Carbon Event
Manager already blocks as appropriate -- and in fact does so with a run
loop, but your app doesn't need to know that.
On Monday, Jun 9, 2003, at 10:10 US/Pacific, phil wrote:
not sure this went to the correct place.. sorry for the dupe.
Hi. I am working with a carbon app and I am just starting to look at
creating some MIDI classes for it. I have done a lot of midi
programming but
not in coreMIDI or OSX yet. All of the examples I have seen are
command line
types with a call to CFRunLoopRun at the end of the main() function.
While
that works, that's is all the app can do once that call is made. I
know.. I
know nothing yet about CFRunLoop stuff but any examples of other
coreMIDI/carbon stuff would be greatly appreciated.. or any hints at
all. I
*think* I am trying to find examples of how you use the thread created
with
MIDICreateClient() in my app.
--
Pete Gontier
http://www.m-audio.com/
_______________________________________________
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.