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 protected]) 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: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to [email protected]
