Re: Strange NSStatusItem Bug
Re: Strange NSStatusItem Bug
- Subject: Re: Strange NSStatusItem Bug
- From: "Crichlow, Eric" <email@hidden>
- Date: Thu, 4 Dec 2003 14:06:38 -0500
On Dec 3, 2003, at 4:39 PM, Eric Schlegel wrote:
>
I think I recognize the problem now. Do you have an NSTimer/CFRunLoopTimer
>
installed that you use for event processing? Do you install it in the
default mode,
>
but not the common modes? In 10.2 and earlier, menu tracking used the
default
>
runloop mode to retrieve events, which allowed timers installed in the
default
>
mode to fire. In apps compiled in 10.3 and later, menu tracking uses the
>
NSEventTrackingRunLoopMode (part of the common modes); if your timer is
>
only installed in the default and not the common modes, it will not fire.
Install your
>
timer in the common modes and it will continue to fire during menu
tracking.
Okay, that takes care of part of the problem, but I fear there is still a
major problem that I'm not going to be able to solve.
Following your advice, my timers now fire. That's a Good Thing. Thanks.
The problem is, I'm relying on data coming through callbacks from the HID
and/or Bluetooth system software in order for me to have data to process
when my timer fires. Apparently, neither HID nor Bluetooth call my
registered callbacks when the NSStatusItem uses the
NSEventTrackingRunLoopMode.
So my guess is that the HID and Bluetooth groups would have to make changes
in the system software similar to what you suggested that I make? I doubt
there's much chance of that happening anytime soon. :(
...Thanx...
...Eric...
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.