• 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
MIDIClient parm in MIDINotifyProc.execute
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

MIDIClient parm in MIDINotifyProc.execute


  • Subject: MIDIClient parm in MIDINotifyProc.execute
  • From: Scott Ruda <email@hidden>
  • Date: Mon, 10 Sep 2001 23:56:54 -0700

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


  • Follow-Ups:
    • Re: MIDIClient parm in MIDINotifyProc.execute
      • From: Bill Stewart <email@hidden>
    • Support of CoreAudio for Multi-Channel
      • From: Christof Faller <email@hidden>
  • Prev by Date: Re: USB Audio Driver
  • Next by Date: DebugAssert when disconnecting a USB MIDI Interface
  • Previous by thread: Re: USB Audio Driver
  • Next by thread: Support of CoreAudio for Multi-Channel
  • Index(es):
    • Date
    • Thread