site_archiver@lists.apple.com Delivered-To: bluetooth-dev@lists.apple.com joe _______________________________________________ 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... Background: To operate within my own specific requirements that I need to kick off a bunch of bluetooth operations from any thread (including the main thread) AND also operate within the IOBluetooth requirement that all operations be performed on a same thread, I've spawned a worker thread that handles all bluetooth operations (it gets awakened whenever there are commands placed in a queue and performs the bluetooth operations asynchronously, while the requesting threads are blocked until completion). So, is it safe or even advisable to call into IOBluetoothUI from this worker thread? My wish is to put up the standard bluetooth discovery dialog to let the user choose which device to connect to. The standard wisdom is never run UI from a non-main thread, but I might not have a choice? This email sent to site_archiver@lists.apple.com