Re: Peripheral dealloced while connecting under ARC?
Re: Peripheral dealloced while connecting under ARC?
- Subject: Re: Peripheral dealloced while connecting under ARC?
- From: Rick Mann <email@hidden>
- Date: Sat, 09 Mar 2013 01:12:15 -0800
On Mar 9, 2013, at 00:18 , Andras Kovi <email@hidden> wrote:
> The problem with requiring the system to retain the peripheral is that once you receive the callback you wouldn't be able to determine which peripheral's interaction initiated the callback. You could say the UUID would be enough. But then having the peripheral stored alongside is not a huge addition. It's annoying and not well documented but can be circumvented easily with some tricks.
Not sure I understand what you're saying here; the peripheral is passed to the callback.
--
Rick
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Bluetooth-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden