• 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: Core Data and undo action names
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Core Data and undo action names


  • Subject: Re: Core Data and undo action names
  • From: Jack Nutting <email@hidden>
  • Date: Tue, 23 Aug 2005 14:41:15 +0200

On 8/22/05, Bill Cheeseman <email@hidden> wrote:
> Some operations not only change a value directly but also trigger secondary
> changes. In such a case, the undo action name should describe the initiating
> operation, not the secondary changes, and undoing it will automatically
> reverse all the secondary changes. But if the secondary changes are
> accomplished through setters that invoke -setActionName: (because sometimes
> these setters are invoked directly as an initiating operation), the
> initiating operation's undo action name gets replaced by the secondary
> change's undo action name. Whichever secondary change happens last wins.

Why not just call setActionName: in your top-level setter *after*
performing the secondary changes?  Then the top-level setter wins.

--
// jack
// http://www.nuthole.com
 _______________________________________________
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

  • Follow-Ups:
    • Re: Core Data and undo action names
      • From: Bill Cheeseman <email@hidden>
References: 
 >Core Data and undo action names (From: Bill Cheeseman <email@hidden>)

  • Prev by Date: Re: NSMutableData short comings?
  • Next by Date: how to Encode the unicode to UTF-8 in cocoa.
  • Previous by thread: Core Data and undo action names
  • Next by thread: Re: Core Data and undo action names
  • Index(es):
    • Date
    • Thread