I agree with Ron that this definitely looks like a user default because it's more a part of the View than the Model, and therefore should go into user defaults instead of the Core Data model.
You often find attributes like this which could go either way. For a less certain example, consider the isItemExpanded (in the outline) state of an object in some kind of hierarchical data model. This could be judged either as View or Model, and the correct answer follows from considering other factors in any given app. For document-based apps, one of the important considerations is that anything you put in the model will put the document into an unsaved state and add an Undo action whenever it is changed. _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) 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: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
