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

Re: MIDIClient parm in MIDINotifyProc.execute


  • Subject: Re: MIDIClient parm in MIDINotifyProc.execute
  • From: Scott Ruda <email@hidden>
  • Date: Tue, 11 Sep 2001 23:35:22 -0700

On Tuesday, September 11, 2001, at 10:14 PM, Bill Stewart <email@hidden> wrote:

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

What do you mean by the 'default MIDIClient'? I see only one constructor for MIDIClient, and I don't see any other way to reference a MIDIClient, e.g. nothing in MIDISetup or any other class. How might one utilize a 'default' MIDIClient instead of constructing one manually?

I am in fact using the MIDIClient constructor 'public MIDIClient (CAFString name, MIDINotifyProc notifyProc)' and am intermittently getting notifications with a null value for the MIDIClient parm in the callback.

Scott


  • Prev by Date: Re: MIDIClient parm in MIDINotifyProc.execute
  • Next by Date: Re: Support of CoreAudio for Multi-Channel
  • Previous by thread: Re: MIDIClient parm in MIDINotifyProc.execute
  • Next by thread: DebugAssert when disconnecting a USB MIDI Interface
  • Index(es):
    • Date
    • Thread