• 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: How can documentForFileName be depricated?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: How can documentForFileName be depricated?


  • Subject: Re: How can documentForFileName be depricated?
  • From: Scott Ellsworth <email@hidden>
  • Date: Wed, 08 Feb 2006 10:00:59 -0800


On Feb 8, 2006, at 9:50 AM, James Bucanek wrote:

For step #2 I was going to call NSDocumentController's documentForFileName. But it says that it's deprecated! That's fine, up to a point. I can imagine that the assumption that all documents are associated with a file path might be unwarranted. I can also easily role my own method for determining if a given document is already opened in a window somewhere.

They want you to replace it with - (id)documentForURL:(NSURL *) absoluteURL, I suspect. According to the docs, it will call documentForFileName if you have overridden it and the url starts with file://


Scott
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden


References: 
 >How can documentForFileName be depricated? (From: James Bucanek <email@hidden>)

  • Prev by Date: How can documentForFileName be depricated?
  • Next by Date: Need help with Japanese (two-byte system) problem
  • Previous by thread: How can documentForFileName be depricated?
  • Next by thread: Need help with Japanese (two-byte system) problem
  • Index(es):
    • Date
    • Thread