Thanks for the answer. In fact I started to establish a thread responsible of all bluetooth=20 stuffs. Worked not so bad but it seem some bluetooth operations stick=20 other ones. For example, while I'm trying to connect every 10s to a device, If I=20 try to get pairedDevices to display preferences, this method returns=20 nothing. Is there a rule for those stuffs ? I'm doing all bluetooth calls in the=20= same thread. Right now I'm trying to use IOBluetoothUI to get a device in the prefs,=20= but the windowController stays white, hangs the app, and display=20 nothing. Is there a difference between using AppKit thread or a custom one ? Any idea ? Thank you ! Le 3 mai 04, =E0 19:05, Marco Pontil a =E9crit :
Hello Yann,
The problem is that the Bluetooth Stack is not designed to run =
on=20
multiple threads. The first thread that makes a call in the stack is=20=
also the only thread that will receive events (and new data is an=20
event) from the stack.
Since your problem seems to be the connection blocking I would=20=
suggest to use the asyncronous API to open the connection. In this way=20=
the caller will not block and once the open connection is completed=20
will be notified of the results (success or failure).
... Marco
On May 2, 2004, at 2:04 AM, Yann Bizeul wrote:
--=20 Yann Bizeul - yann at tynsoe.org http://projects.tynsoe.org/ [demime 0.98b removed an attachment of type application/pkcs7-signature which had a name of smime.p7s] _______________________________________________ bluetooth-dev mailing list | bluetooth-dev@lists.apple.com Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/bluetooth-dev Do not post admin requests to the list. They will be ignored.