On May 2, 2013, at 15:25 , Andras Kovi <allprog@gmail.com> wrote:
you shouldn't do that. Callbacks can easily be messed up, additionally, CB doesn't tolerate well the regular/stressful creation/deletion of managers. There have been several discussions on this topic, you may look them up jn the list archives.
Thanks, Andras; I'll stick to a single CM, and use some method to map CBPeripherals to my Core Data entities. Apple could help a lot by allowing me to set arbitrary keys on CBPeripheral objects.
I personally find ReactiveCocoa to be a really useful tool for these kind of situations. It's much easier for me to think in terms of signals than delegates and callbacks (usually messed up with switch and if-then statements).
Wow, this seems pretty amazing; I'll have to consider it for my next project (or even this one, but not today). Thanks for pointing it out! -- Rick _______________________________________________ Do not post admin requests to the list. They will be ignored. Bluetooth-dev mailing list (Bluetooth-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/bluetooth-dev/site_archiver%40lists.... This email sent to site_archiver@lists.apple.com