Hi Ron,
thanks for the reply. I agree just storing the "last known thing that
the user was looking at" is doable, wouldn't require a non-MVC model-
based hack, and would make for a much smaller user defaults file - as
there's only 3 selections being stored (1x Company, 1x Department and
1x
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 th
On 25/01/2010, at 8:42 PM, Ken Tabb wrote:
On 25 Jan 2010, at 9:38, Tabb, Ken wrote:
Hi folks,
I have a Core Data app that needs to remember state of selected items
between launches.
The app's UI is a bit like iTunes (containers / playlists down the
side and contents show in a big tablevie
Doh... sorry about the length of that message, it included the various
draft versions, so please ignore it (unless you like seeing the pain
someone goes through when trying to state their problem concisely!)
Below is the properly edited version, and I'd be grateful for any
advice you can gi
Hi folks,
I have a Core Data app that needs to remember state of selected items
between launches.
The app's UI is a bit like iTunes (containers / playlists down the
side and contents show in a big tableview), except that there are 3
layers of containment, so rather than Playlists and Trac
