Re: Strange NSStatusItem Bug
Re: Strange NSStatusItem Bug
- Subject: Re: Strange NSStatusItem Bug
- From: Eric Schlegel <email@hidden>
- Date: Wed, 3 Dec 2003 15:39:32 -0800
On Dec 3, 2003, at 3:16 PM, Crichlow, Eric wrote:
So, the new, succinct version of the problem is that when a
NSStatusItem
menu is pulled down, application processing freezes until the menu is
dismissed.
This seems to only be the case in 10.3. In 10.2, application
processing
was not frozen when an NSStatusItem menu was pulled down.
Since the problem starts when I recompile under 10.3, I would
assume
that some library/framework has been updated, and the changes are
what's
behind this
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.
-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.