Re: Use 2 central Manager
Re: Use 2 central Manager
- Subject: Re: Use 2 central Manager
- From: Alpwise iOS Dev <email@hidden>
- Date: Mon, 28 Jan 2013 10:51:40 +0100
Hi,
thanks for the reply. I fixed my code and used only one CM. As Apple permit to create multiple instance of CM, i was thinking that was possible. But like you say it's a disaster.
Cheers, Samuel Le 25 janv. 2013 à 16:09, András Kövi a écrit : When I tried that, the results were disastrous. Start a request on one manager and receive the callback on the other... It's possible that I messed up something but not very likely. However, the things you describe are easily handleable by one CM. Why would you use two?
I suggest you try to optimize your use case for one CM.
Note: The CBPeripheral is an internal object and it is connected to the CentralManager. You shouldn't suppose anything on the lifecycle of the CBPeriperal or its values. However, you start a connection to it, then you must keep the reference as long as the connection is alive, otherwise you'll get a warning that the peripheral is being deallocated while it is connected or the CM is trying to connect to it. This is an annoying behavior but we have to live with it.
Cheers, Andras
|
_______________________________________________
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