Re: Client notification wierdiness
Re: Client notification wierdiness
- Subject: Re: Client notification wierdiness
- From: Kurt Revis <email@hidden>
- Date: Tue, 30 Apr 2002 18:05:27 -0700
On Tuesday, April 30, 2002, at 09:04 AM, Michel Pollet wrote:
I have a notification callback for a client. Apparently that is called
'lots'
if I create virtual destinations/sources on that client (like, when it's
created, when theres a setproperty on it)
But, that notification is never called if *another* process
creates/register
new destinations/sources.
Are you sure that's what's going on? I always get a notification when
any client's virtual/source destination changes (as well as when
hardware devices are added or removed). I've spent a lot of time
exercising this, and I've never seen the behavior you describe.
I've noted this many times on the list, but I'll say it again: your
notification proc needs to be reentrant. If you call a CoreMIDI
function* from your notification proc, CoreMIDI could call into your
notification proc again while doing its own work. If you don't know this
is happening, the results can be pretty baffling. Could this be your
problem?
(* or perhaps any function that runs the run loop -- I'm not sure)
--
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.