Preserving user interface properties in Core Data documents
Preserving user interface properties in Core Data documents
- Subject: Preserving user interface properties in Core Data documents
- From: "Sean McBride" <email@hidden>
- Date: Thu, 26 Apr 2007 15:59:26 -0400
- Organization: Rogue Research
Hi all,
What is the recommended way to preserve UI properties as part of a
document? For example: window sizes, window position, table column
sizes, etc.
My application uses Core Data and Cocoa Bindings, and can require the
latest OS.
Should I create an entity to describe UI properties? I guess that would
work, but would it not also make the document 'dirty' just because the
window size changed? I know that many view classes let one store their
properties in the defaults (like NSWindow's setFrameAutosaveName:), but
that's no good because I need it in the document.
I've searched for discussions of this, but not found anything of use.
Thanks for any suggestions.
--
____________________________________________________________
Sean McBride, B. Eng email@hidden
Rogue Research www.rogue-research.com
Mac Software Developer Montréal, Québec, Canada
_______________________________________________
Cocoa-dev mailing list (email@hidden)
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