expected behavior of AU Component Manager scans?
expected behavior of AU Component Manager scans?
- Subject: expected behavior of AU Component Manager scans?
- From: "Ross Bencina" <email@hidden>
- Date: Mon, 19 Jul 2010 21:01:43 +1000
Hi
I'm enumerating AU plugins using component manager calls (FindNextComponent
etc). I seem to be observing some anomalous behavior with regard to
visibility of installed plugins. For example:
- Sometimes, adding a plugin to the AU components folder while my app is
running, and doing a rescan (rerunning a FindNextComponent enumeration)
doesn't cause the plugin to be found. Next time I restart my App my App can
see it.
- Sometimes, after removing a plugin from the AU components folder, it still
appears in the FindNextComponent scan, even after restarting my App.
Apparently only rebooting makes it go away.
I assume its caching things, or perhaps in the latter case, the plugins
themselves are staying resident. Is there any way I can force it to rescan
the filesystem during a program run to find new plugins, and to unload
components between program runs?
Is there any documentation available about the expected behavior of
Component Manager in these kind of cases? If I can't get it to behave how
I'd like, I'd at least like to explain to my users what they can expect.
Any thoughts?
Thanks
Ross.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Coreaudio-api mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden