Skip navigation.
 
mlPreserving user interface properties in Core Data documents
FROM : Sean McBride
DATE : Thu Apr 26 21:59:26 2007

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_removed>
Rogue Research                        www.rogue-research.com
Mac Software Developer              Montréal, Québec, Canada

Related mailsAuthorDate
mlPreserving user interface properties in Core Data documents Sean McBride Apr 26, 21:59
mlRe: Preserving user interface properties in Core Data documents I. Savant Apr 26, 22:33
mlRe: Preserving user interface properties in Core Data documents I. Savant Apr 26, 22:35