• 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
Re: Some more questions on NSOpenPanel
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Some more questions on NSOpenPanel


  • Subject: Re: Some more questions on NSOpenPanel
  • From: "David M. Cotter" <email@hidden>
  • Date: Tue, 29 Sep 2009 15:52:14 -0700

originally from Frameworks IT list:

Vlad:
For some reason cmd-A does not work in our NSOpenPanel to select the current contents of the browser but navigation keystrokes do work. Is there something obvious that I am missing? Any clues?


Corbin:
Do you have an edit menu with Select All (Cmd-A)? If not..you might have to add one. Others may chime in if there is a different work around.

Vlad:
Our app does have Select All in Edit menu but since NSOpenModal is run as modal dialog, it is disabled with the rest of menu commands. I did a quick (far from exhaustive) survey and see that Apple apps enable Select All when modal dialog is up but non-Apple apps disable it.

The fully disabled Edit menu worked fine with NavServices (select all did select files in Open dialog) but is different in Cocoa.


Are you saying that if Select All is enabled when NSOpenPanel is up, then it will magically work? How does NSOpenPanel know that this command is selected if it is processed by the app’s event handling system? Sorry if it is something obvious but I am not sure I understand how it is supposed to work.

Corbin:
Yes -- it will work. The reason why, is because the command is sent up the responder chain.

Me:

well, sadly it still does not work.

Just before we put up the dialog, we enable undo, cut, copy, paste, clear, and select all. these items all have the correct HICommand assigned (eg: "select all" has kHICommandSelectAll as it's "tag")

the only possibly different thing is that these items have their "action" set to something other than default. would this make a difference?
other than that, what could be causing this to fail? all items end up disabled, and it's not us disabling them._______________________________________________


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: Some more questions on NSOpenPanel
      • From: Kyle Sluder <email@hidden>
  • Prev by Date: Re: Suggestions for debugging “EXC_BAD_ACCESS” - followup
  • Next by Date: re: Strange Core Data save behaviour ("required relationship nil"... when it is set the line before saving)
  • Previous by thread: Re: Cocoa-dev Digest, Vol 6, Issue 1394
  • Next by thread: Re: Some more questions on NSOpenPanel
  • Index(es):
    • Date
    • Thread