Re: MIDIClient parm in MIDINotifyProc.execute
Re: MIDIClient parm in MIDINotifyProc.execute
- Subject: Re: MIDIClient parm in MIDINotifyProc.execute
- From: Bill Stewart <email@hidden>
- Date: Tue, 11 Sep 2001 12:38:27 -0700
This will be non-null if you've used the following call on MIDIClient:
public MIDIClient (CAFString name, MIDINotifyProc notifyProc)
If you're using the default MIDIClient, then you're notification
param will be null
Bill
On Monday, September 10, 2001, at 11:56 PM, Scott Ruda wrote:
I'm using the Java APIs to access the CoreAudio MIDI services and
was wondering if it is expected behavior for the MIDIClient parm
in the MIDINotifyProc.execute callback to always return a null
value. (That's what I always get). Normally I presume one would
only ever create one MIDIClient per application, and therefore it
would be OK to assume that parm would always be the one for the
application. But I imagine that the point of that parm would be in
case you wanted to share a notify proc with multiple MIDIClient
instances in the same application. I currently only have one
client in my app, so I guess I can safely ignore the parm, but it
seems like it 'should' be a valid MIDIClient reference, no?
I noticed that in the native version of MIDINotifyProc there is no
MIDIClient parm. It seems odd that it is different in the Java
API...
Scott
_______________________________________________
coreaudio-api mailing list
email@hidden
http://www.lists.apple.com/mailman/listinfo/coreaudio-api
mailto:email@hidden
tel: +1 408 974 4056
__________________________________________________________________________
Cat: "Leave me alone, I'm trying to nap... Ah, What's that clicking
noise?"
__________________________________________________________________________