Bluetooth data not processed in NSEventTrackingRunLoopMode?
Bluetooth data not processed in NSEventTrackingRunLoopMode?
- Subject: Bluetooth data not processed in NSEventTrackingRunLoopMode?
- From: "Crichlow, Eric" <email@hidden>
- Date: Wed, 31 Dec 2003 14:47:20 -0500
In 10.3, the system software changed such that menu tracking occurs in
NSEventTrackingRunLoopMode, whereas previously it occurred in the default
mode.
Because of that, now, I stop getting Bluetooth data from the OS (using
either the old callback method or the new setDelegate method) when my app's
NSStatusMenu is pulled down. This is absolutely unacceptable for me, since
my Bluetooth device's whole purpose is to be used as the system mouse. Now
it locks up when the user uses's the device to select my app's menu.
Does Bluetooth processing only take place in the default mode? Is there
something I can do to get around this huge problem?
...Thanx...
...Eric...
_______________________________________________
bluetooth-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/bluetooth-dev
Do not post admin requests to the list. They will be ignored.