Re: MIDI driver monitoring -- bad destination?
Re: MIDI driver monitoring -- bad destination?
- Subject: Re: MIDI driver monitoring -- bad destination?
- From: Kurt Revis <email@hidden>
- Date: Mon, 11 Mar 2002 23:43:32 -0800
On Monday, March 11, 2002, at 10:41 AM, Doug Wyatt wrote:
Thanks Kirt, good catch. It'll be fixed in the next rev.
OK. Just to check: Am I safe in assuming that I can check the version of
the CoreMIDIServer bundle, and if it is later than the version installed
in 10.1.3, just go ahead and use the provided MIDIEndpointRef as-is?
Like this:
CFBundleRef coreMIDIServerBundle;
UInt32 version;
mNeedsMonitorPointerWorkaround = false;
coreMIDIServerBundle =
CFBundleGetBundleWithIdentifier(CFSTR("com.apple.audio.midi.CoreMIDIServer"
));
if (coreMIDIServerBundle) {
version = CFBundleGetVersionNumber(coreMIDIServerBundle);
if (version <= 0x15108000) // 15.1, the version as of 10.1.3
mNeedsMonitorPointerWorkaround = true;
}
(and then use mNeedsMonitorPointerWorkaround as appropriate later on)
Or is it possible that the bundle's identifier could change in the
future?
Alternatively, I could use CFMainBundle() from my driver, which returns
the CoreMIDIServer bundle--but I am not sure that I should rely on that
always staying the same. Or would it be safer to call CFBundleCreate()
with the path /System/Library/Frameworks/CoreMIDIServer.framework, since
that should not change (since changing the framework's path would break
anything linked against it)?
If CoreMIDI provided a version number in its API (like
kCFCoreFoundationVersionNumber for CoreFoundation) then I wouldn't have
to worry about all this bundle stuff. I've filed a feature request for
that.
Thanks!
--
Kurt Revis
email@hidden
_______________________________________________
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.