May 2013 - Bluetooth-dev - lists.apple.com

Re: Multiple CBCentralManagers?
by John Earl 02 May '13

02 May '13

_______________________________________________ Do not post admin requests to the list. They will be ignored. Bluetooth-dev mailing list (Bluetooth-dev(a)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(a)lists.apple.com

1 0

Re: Multiple CBCentralManagers?
by John Earl 02 May '13

02 May '13

On 2 May 2013, at 23:40, Rick Mann wrote: > > On May 2, 2013, at 15:25 , Andras Kovi <allprog(a)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. Write a category with getters and setters implemented with associated objects. _______________________________________________ Do not post admin requests to the list. They will be ignored. Bluetooth-dev mailing list (Bluetooth-dev(a)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(a)lists.apple.com

1 0

Re: Multiple CBCentralManagers?
by Rick Mann 02 May '13

02 May '13

On May 2, 2013, at 15:25 , Andras Kovi <allprog(a)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(a)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(a)lists.apple.com

1 0

Re: Multiple CBCentralManagers?
by Andras Kovi 02 May '13

02 May '13

Hi Rick, 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. If I could suggest you, try to use some loosely coupled solution, e.g. notifications. The "peripheral retrieved" callback would simply have to publish a corresponding notification that your local code could listen to. This way you need to access only the manager but not change the delegate. But I think you know these kind of patterns better than I do. 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). Regards, Andras On 2013.05.03., at 0:02, Rick Mann <rmann(a)latencyzero.com> wrote: > Is it okay to have multiple CBCentralManagers around? What happens if I instantiate a CM, use it to get a CBPeripheral, then deallocate that CM but keep the CBPeripheral around? What if I have one CM per peripheral? > > I have a situation where I'm storing a representation of my CBPeripheral in Core Data (it has a UUID property). When that representation is later fetched from Core Data, I need to get a new CBPeripheral instance for it. Unfortunately I don't have easy access to the "main" CM I'm using in my app for discovery, and even so, having a "dedicated" CM allows for straightforward retrieval of a CBPeripheral in -awakeFromFetch. > > -- > Rick > > > > > _______________________________________________ > Do not post admin requests to the list. They will be ignored. > Bluetooth-dev mailing list (Bluetooth-dev(a)lists.apple.com) > Help/Unsubscribe/Update your Subscription: > https://lists.apple.com/mailman/options/bluetooth-dev/allprog%40gmail.com > > This email sent to allprog(a)gmail.com _______________________________________________ Do not post admin requests to the list. They will be ignored. Bluetooth-dev mailing list (Bluetooth-dev(a)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(a)lists.apple.com

1 0

Multiple CBCentralManagers?
by Rick Mann 02 May '13

02 May '13

Is it okay to have multiple CBCentralManagers around? What happens if I instantiate a CM, use it to get a CBPeripheral, then deallocate that CM but keep the CBPeripheral around? What if I have one CM per peripheral? I have a situation where I'm storing a representation of my CBPeripheral in Core Data (it has a UUID property). When that representation is later fetched from Core Data, I need to get a new CBPeripheral instance for it. Unfortunately I don't have easy access to the "main" CM I'm using in my app for discovery, and even so, having a "dedicated" CM allows for straightforward retrieval of a CBPeripheral in -awakeFromFetch. -- Rick _______________________________________________ Do not post admin requests to the list. They will be ignored. Bluetooth-dev mailing list (Bluetooth-dev(a)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(a)lists.apple.com

1 0

RE: CoreBluetooth on OS X
by Joakim Fernstad 02 May '13

02 May '13

CoreBluetooth seem to only be includable through IOBluetooth. I agree with you guys that it's weird they decided to go this route. Trying to link directly with CoreBluetooth gives this linker error. ld: cannot link directly with /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.8.sdk/System/Library/Frameworks/IOBluetooth.framework/Frameworks/CoreBluetooth.framework/CoreBluetooth. Link against the umbrella framework 'IOBluetooth.framework' instead. for architecture x86_64 Joakim -----Original Message----- From: dave-ble(a)greylogic.com [mailto:dave-ble@greylogic.com] Sent: Thursday, May 02, 2013 1:09 PM To: Joakim Fernstad Cc: Rick Mann; bluetooth-dev(a)lists.apple.com Bluetooth Subject: Re: CoreBluetooth on OS X I have had to deal with the same issues as Rick. I have the following everywhere I need to import the CoreBluetooth header files. #ifdef __OSX_PLATFORM__ # import <IOBluetooth/IOBluetooth.h> #else # import <CoreBluetooth/CoreBluetooth.h> #endif I don't understand why I can't just import CoreBluetooth.h on both platforms since all I want is BLE. -- dave On May 2, 2013, at 1:00 PM, Joakim Fernstad <jfernstad(a)stratos.com> wrote: > CoreBluetooth is only for BLE and it exist for OS X as well as for iOS. It's the same interface for both platforms. > > IOBluetooth is for 'regular' Bluetooth which is not allowed (unless you do MFI) for iOS and hence only exist for OS X. > > Joakim > > -----Original Message----- > From: bluetooth-dev-bounces+jfernstad=stratos.com(a)lists.apple.com > [mailto:bluetooth-dev-bounces+jfernstad=stratos.com@lists.apple.com] > On Behalf Of Rick Mann > Sent: Thursday, May 02, 2013 12:11 PM > To: bluetooth-dev(a)lists.apple.com Bluetooth > Subject: CoreBluetooth on OS X > > Why is it IOBluetooth on OS X and note CoreBluetooth? For the longest time, sharing Quartz 2D code between iOS and OS X was a pain, because you had to include different header files. Now I find it's the same with Core Bluetooth. > > > > -- > Rick > > > > > _______________________________________________ > Do not post admin requests to the list. They will be ignored. > Bluetooth-dev mailing list (Bluetooth-dev(a)lists.apple.com) > Help/Unsubscribe/Update your Subscription: > https://lists.apple.com/mailman/options/bluetooth-dev/jfernstad%40stra > tos.com > > This email sent to jfernstad(a)stratos.com > > _______________________________________________ > Do not post admin requests to the list. They will be ignored. > Bluetooth-dev mailing list (Bluetooth-dev(a)lists.apple.com) > Help/Unsubscribe/Update your Subscription: > https://lists.apple.com/mailman/options/bluetooth-dev/dave-ble%40greyl > ogic.com > > This email sent to dave-ble(a)greylogic.com _______________________________________________ Do not post admin requests to the list. They will be ignored. Bluetooth-dev mailing list (Bluetooth-dev(a)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(a)lists.apple.com

1 0

Re: CoreBluetooth on OS X
by dave-ble＠greylogic.com 02 May '13

02 May '13

I have had to deal with the same issues as Rick. I have the following everywhere I need to import the CoreBluetooth header files. #ifdef __OSX_PLATFORM__ # import <IOBluetooth/IOBluetooth.h> #else # import <CoreBluetooth/CoreBluetooth.h> #endif I don't understand why I can't just import CoreBluetooth.h on both platforms since all I want is BLE. -- dave On May 2, 2013, at 1:00 PM, Joakim Fernstad <jfernstad(a)stratos.com> wrote: > CoreBluetooth is only for BLE and it exist for OS X as well as for iOS. It's the same interface for both platforms. > > IOBluetooth is for 'regular' Bluetooth which is not allowed (unless you do MFI) for iOS and hence only exist for OS X. > > Joakim > > -----Original Message----- > From: bluetooth-dev-bounces+jfernstad=stratos.com(a)lists.apple.com [mailto:bluetooth-dev-bounces+jfernstad=stratos.com@lists.apple.com] On Behalf Of Rick Mann > Sent: Thursday, May 02, 2013 12:11 PM > To: bluetooth-dev(a)lists.apple.com Bluetooth > Subject: CoreBluetooth on OS X > > Why is it IOBluetooth on OS X and note CoreBluetooth? For the longest time, sharing Quartz 2D code between iOS and OS X was a pain, because you had to include different header files. Now I find it's the same with Core Bluetooth. > > > > -- > Rick > > > > > _______________________________________________ > Do not post admin requests to the list. They will be ignored. > Bluetooth-dev mailing list (Bluetooth-dev(a)lists.apple.com) > Help/Unsubscribe/Update your Subscription: > https://lists.apple.com/mailman/options/bluetooth-dev/jfernstad%40stratos.c… > > This email sent to jfernstad(a)stratos.com > > _______________________________________________ > Do not post admin requests to the list. They will be ignored. > Bluetooth-dev mailing list (Bluetooth-dev(a)lists.apple.com) > Help/Unsubscribe/Update your Subscription: > https://lists.apple.com/mailman/options/bluetooth-dev/dave-ble%40greylogic.… > > This email sent to dave-ble(a)greylogic.com _______________________________________________ Do not post admin requests to the list. They will be ignored. Bluetooth-dev mailing list (Bluetooth-dev(a)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(a)lists.apple.com

1 0

RE: CoreBluetooth on OS X
by Joakim Fernstad 02 May '13

02 May '13

CoreBluetooth is only for BLE and it exist for OS X as well as for iOS. It's the same interface for both platforms. IOBluetooth is for 'regular' Bluetooth which is not allowed (unless you do MFI) for iOS and hence only exist for OS X. Joakim -----Original Message----- From: bluetooth-dev-bounces+jfernstad=stratos.com(a)lists.apple.com [mailto:bluetooth-dev-bounces+jfernstad=stratos.com@lists.apple.com] On Behalf Of Rick Mann Sent: Thursday, May 02, 2013 12:11 PM To: bluetooth-dev(a)lists.apple.com Bluetooth Subject: CoreBluetooth on OS X Why is it IOBluetooth on OS X and note CoreBluetooth? For the longest time, sharing Quartz 2D code between iOS and OS X was a pain, because you had to include different header files. Now I find it's the same with Core Bluetooth. -- Rick _______________________________________________ Do not post admin requests to the list. They will be ignored. Bluetooth-dev mailing list (Bluetooth-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/bluetooth-dev/jfernstad%40stratos.c… This email sent to jfernstad(a)stratos.com _______________________________________________ Do not post admin requests to the list. They will be ignored. Bluetooth-dev mailing list (Bluetooth-dev(a)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(a)lists.apple.com

1 0

CoreBluetooth on OS X
by Rick Mann 02 May '13

02 May '13

Why is it IOBluetooth on OS X and note CoreBluetooth? For the longest time, sharing Quartz 2D code between iOS and OS X was a pain, because you had to include different header files. Now I find it's the same with Core Bluetooth. -- Rick _______________________________________________ Do not post admin requests to the list. They will be ignored. Bluetooth-dev mailing list (Bluetooth-dev(a)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(a)lists.apple.com

1 0

RE: Immediate disconnect after connection attempts?
by Steve Childerley 02 May '13

02 May '13

_______________________________________________ Do not post admin requests to the list. They will be ignored. Bluetooth-dev mailing list (Bluetooth-dev(a)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(a)lists.apple.com

1 0