• 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: A simple request
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: A simple request


  • Subject: Re: A simple request
  • From: Rosyna <email@hidden>
  • Date: Mon, 3 Dec 2001 20:57:50 -0700

nil works. It's what I use. No crashes.

There seems to be an Apple problem here. In the classic macos, you could set where applications went for open and save dialog boxes (user settable) "Application, Documents, Last folder used in application".

If the user is going to open or save a file that will only come from a specific path (say saving Frogblast icons), but all means use the path. But for ALL other open/save paths please use nil or @"".

All cocoa devs should obey this because it's the right thing Go find a novice computer user, ask them to open then save a file. Ask them to open the file they just saved. If they saved it to another path, they are very unlikely to find where they saved it again. This is especially true if you have to assist them in saving the file (say, to an external 57gig firewire drive). A novice user is not going to understand how to get back to it. Even more so now that the Open/Save dialogs use horizontal scrollbars.

Ack, at 12/3/01, Mark T said:

Can cocoa developers please not set a default path for open and save dialog boxes? Instead set nil. This will go to the last folder the user used in the application, which is what he may want to do if he has to open multiple files.
--


I think you mean @"". Setting these to nil will cause your application to crash, as stated in NSOpenPanel and NSSavePanel docs. And while I'm not saying whether this is a good or bad suggestion(it depends a lot on the situation - a user preference might not be a bad idea), your own statement's use of the word may indicates that this is merely a possibility, not a definite. I don't mean to be critical, but this admission seems to take some weight away from your initial suggestion(if the user only *may* want that, why *should* all cocoa devs obey this?).

Just my one and a half cents...

--



Sincerely,
Rosyna Keller
Technical Support/Holy Knight/Always needs a hug

Unsanity: Unsane Tools for Insane People


References: 
 >Re: A simple request (From: Mark T <email@hidden>)

  • Prev by Date: Re: Question
  • Next by Date: JavaBridge
  • Previous by thread: Re: A simple request
  • Next by thread: JavaBridge
  • Index(es):
    • Date
    • Thread