I'm not even sure bluetooth really has anything to do with this problem, but it occurs in my bluetooth event callback, so that's where I'm focussing my attention. I'm using a bluetooth tablet (or whiteboard) to control the Mac by mapping the points generted by the tablet to pixels on the screen and generating mouse events (using CGPostMouseEvent) on the relative screen coordinates. Essentially, the tablet becomes a mouse. The application that controls processing the bluetooth events and generating the mouse events also has a user interface window built with Interface Builder. On this window are several buttons and 2 NSTableViews. If, in the bluetooth event callback, I generate a mouse event that clicks on one of the buttons (which has a connection to a target method in the code) or a populated row in the table (the NSTableView does not have a connection set), OS X's user interface locks up. What I mean by "locks up" is that I can move the mouse (with the actual mouse... bluetooth events are no longer processed) but anything I click on gives me no response. Alt-Apple-Esc does nothing. However, it's just the user interface, not the OS itself, that is frozen. Other applications continue to update their windows (though I can't select them), iTunes continues to play music, and I can log into the system from another Mac. I set a breakpoint on the first line of code in the action method for the button. I never make it to that breakpoint. So my belief is that the lockup comes after I fire off the mouse event but before the action method gets called. Could this be caused by doing too much (initiating a mouse event) within the bluetooth event callback? ...Thanx... ...Eric Crichlow... ...GTCO CalComp... _______________________________________________ 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.