• 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
restorableStateKeyPaths versus invalidateRestorableState
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

restorableStateKeyPaths versus invalidateRestorableState


  • Subject: restorableStateKeyPaths versus invalidateRestorableState
  • From: Daryle Walker <email@hidden>
  • Date: Sun, 21 Sep 2014 14:17:57 -0400

These are two methods in NSResponder and they deal with user-interface restore.

The docs say that +restorableStateKeyPaths can lead to not needing to use -encodeRestorableStateWithCoder: and -restoreStateWithCoder:. Since those key-path attributes are supposed to be watched with KVO, shouldn’t explicitly calling -invalidateRestorableState also be unnecessary (assuming full coverage)? Can anyone confirm?

—
Daryle Walker
Mac, Internet, and Video Game Junkie
darylew AT mac DOT com

_______________________________________________

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


  • Prev by Date: Re: Question on OS X app submission
  • Next by Date: RE: return string that is the difference between two other strings
  • Previous by thread: Re: Custom layout and constraints
  • Next by thread: WebView and User Interface Restore
  • Index(es):
    • Date
    • Thread