• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
inappropriate tool palette activation problem
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

inappropriate tool palette activation problem


  • Subject: inappropriate tool palette activation problem
  • From: John Richetta <email@hidden>
  • Date: Tue, 16 Oct 2007 10:50:52 -0700

I have a problem, and it might very well be basic, but I'm hoping it rings a bell, and some kind soul will help me.

I've looked around in Google, and through mail list archives, but some topics, due to the generic nature of the words appropriate for describing them, are hard to research.

The problem is that my application's tool palettes seem to misbehave quite a bit, with respect to window activation.

Generally, all windows - *including tool palettes* as well as main document windows - require a click to activate them. This, in spite of the documentation stating that utility panels stay in their own layer.

Tool palettes don't seem very common on OS X, but those I've examined don't have this problem.

I've tried tinkering with most of the obvious window attributes (floating aka "utility," non-activating, and other doubtlessly irrelevant attributes like "works when modal" and "becomes key only if needed") in IB and programmatically, and nothing I've done so far appears to affect this behavior.

I haven't thought of anything else that would be causing this, except perhaps something I'm doing actively, that's bad, perhaps in misusing some part of the frameworks.

It might be coincidental, but I also find that I also have some odd behavior related to didBecomeMain and didResignMain notifications (the only way I've discovered to receive window activation events - amazing!). I find that no matter what I do, all document windows seem to report being activated and deactivated, whenever just one's state changes. This certainly isn't what I want, and seems like it might somehow be related - but perhaps not.

Any suggestions (about either problem)?

-jar
_______________________________________________

Cocoa-dev mailing list (email@hidden)

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:
This email sent to email@hidden


  • Follow-Ups:
    • Re: inappropriate tool palette activation problem
      • From: Scott Stevenson <email@hidden>
  • Prev by Date: Re: Question about laterDate: and earlierDate:
  • Next by Date: Re: Kludges when binding to 'value' of Menu Items
  • Previous by thread: Re: warning: assignment makes integer from pointer without a cast
  • Next by thread: Re: inappropriate tool palette activation problem
  • Index(es):
    • Date
    • Thread