• 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 user-defined fields
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Core Data user-defined fields

  • Subject: Re: Core Data user-defined fields
  • From: Jerry Krinock <email@hidden>
  • Date: Mon, 02 May 2016 13:55:41 -0700
In a similar situation, I defined one Property to represent both your Required (A, B, C) and User-defined properties, and wrote some business logic to ensure that the Required properties were always present.  A variation would be that this user-interfacing Property is a dependent property, connecting to the appropriate A, B, C or User-defined properties in the model via custom accessors.  Don’t forget +keyPathsForValuesAffecting<Whatever>.

In the user interface, I put one pair of [+][-] buttons at the bottom left of the table to add rows, and another pair of [+][-] buttons at the top right of the table to add columns.


_______________________________________________

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
References: 
 >Core Data user-defined fields (From: Trygve Inda <email@hidden>)

  • Prev by Date: Core Data user-defined fields
  • Next by Date: Re: undomanger performance
  • Previous by thread: Core Data user-defined fields
  • Next by thread: Presenting view controller over another changes its size
  • Index(es):
    • Date
    • Thread