site_archiver@lists.apple.com Delivered-To: bluetooth-dev@lists.apple.com Good luck. joe On Jan 18, 2006, at 1:42 AM, Miguel Menchu wrote: _______________________________________________ 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: http://lists.apple.com/mailman/options/bluetooth-dev/site_archiver%40lists.a... You can use the objective-C apis in a non gui application or shared library or in most any other kind of user space executable. The only places where I've seen UI appear up in my RFCOMM project is when I use the IOBluetoothBluetoothDeviceSelectorController class -- as would be expected -- and when I call IOBluetoothDevice's - requestAuthentication: method on an unpaired device. Anyhow, I actually see an IOBluetoothDeviceInquiryRef in the flat C headers. Remember that Device Inquiry is an OS 10.4 only feature, and your headers or Xcode could be out of date? Continuing work on my c code (non gui, IOBluetoothUserLib.h) I tried creating an object of type IOBluetoothDeviceInquiry in order to start an inquire, except that that class is defined for objective-c and not for my non-gui c. I tried appending "ref" to make it IOBluetoothDeviceInquiryRef thinking maybe.... but nothing. Is there a standard re-naming convention I'm not following... ? How can i discover other bluetooth devices using non-gui c api? In case you're wondering, i'm choosing non-gui because i'm hoping to include his in a dashboard widget. Thanks a lot for your help. - Miguel. This email sent to site_archiver@lists.apple.com