On Mon, Oct 13, 2008 at 9:23 PM, Rick Mann <[EMAIL PROTECTED]> wrote: > I've been assigned to work on my company's Mac product, which includes a > Status Item. One of the things we've noticed is that if you click on a > neighboring status item (single click to pop open its menu), and the hover > over ours, our menu doesn't open. > > Contrast this with the Apple status items: for example, if you click on the > time machine item, its menu opens. If you then hover on the speaker item > (which is just to the right on my menu bar), the time machine menu closes, > and the speaker menu opens. If you go back over the TM item, the reverse > happens. > > If you do the same on our item, and move to an Apple item, it behaves as > expected. If you then move back to our item, it does not re-open. > > Note that you can click and hold and experience the same behavior. > > Does anyone know what I need to do to get my item to behave properly (that > is, open its menu when the mouse goes over it after having opened a > neighboring menu)?
Apple's "status items" behave better because they're not status items at all, but rather menu extras, which are implemented NSMenuExtra. They are essentially better in every way and are, surprise surprise, a private API. If using a private API doesn't worry you, then google should turn up plenty of information for using them. If using a private API does worry you (and it probably should), then you'll have to settle for the fact that your NSStatusItem is going to be pretty bad by comparison. If it's any consolation, a lot of third-party apps use them so your users are probably used to the discrepancy. Mike _______________________________________________ Cocoa-dev mailing list ([email protected]) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to [EMAIL PROTECTED]
