• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Questions about Run Loops
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Questions about Run Loops


  • Subject: Re: Questions about Run Loops
  • From: Geoffrey Schmit <email@hidden>
  • Date: Thu, 17 Nov 2005 08:37:12 -0600

On 16/11/2005 at 3:14 PM -0800, Joseph Kelly <email@hidden> wrote:

> It is absolutely not advisable to use a dedicated worker thread to
> call the Bluetooth api's. It's unreliable, and you won't even be able
> to use IOBluetoothUI.framework.

I've ensured that my framework functions that end up calling into the IOBluetoothUI framework are always called on the application's UI thread.  If I ensure this, what problems would I encounter if I create a thread that is responsible for calling into the IOBluetooth framework and have my other framework functions pass messages to this thread?  If I create a thread using pthreads, will that thread have an associated run loop or do I have to create one explicitly?  The documentation I've read was not clear on this point.

Thanks for any insight!

geoff
 _______________________________________________
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

  • Follow-Ups:
    • Re: Questions about Run Loops
      • From: Joseph Kelly <email@hidden>
References: 
 >Re: Questions about Run Loops (From: Joseph Kelly <email@hidden>)

  • Prev by Date: Re: Questions about Run Loops
  • Next by Date: Re: Questions about Run Loops
  • Previous by thread: Re: Questions about Run Loops
  • Next by thread: Re: Questions about Run Loops
  • Index(es):
    • Date
    • Thread