On Aug 26, 2014, at 11:39 AM, Keary Suska wrote:
>> * When should I do this? before, or after my calls to CoreData?
>
> You would tend to register undo action in the order they need to be *undone*,
> but logically if you need to make changes in response to changes made to a
> context, you woul
On Aug 26, 2014, at 7:34 AM, Motti Shneor wrote:
> Let's say we have the standard "Organization"->"Department"->"Employee"
> application with two level ordered relations, Each Document representing a
> distinct persistent store with a single Organization and its departments and
> employes. The
On Tue, 26 Aug 2014 16:34:30 +0300, Motti Shneor said:
>In my document NSWindowController, there are two references, to the
>
>@property (atomic, readwrite, weak) NSManagedObject
>*currentDepartment; // and
>@property (atomic, readwrite, weak) NSManagedObject *currentEmployee;
>
>(I know this ex
Thanks Keary, I will try to focus on one simple hypothetic case, so you (and
others) can address my question more specifically.
Let's say we have the standard "Organization"->"Department"->"Employee"
application with two level ordered relations, Each Document representing a
distinct persistent
On Aug 24, 2014, at 9:07 AM, Motti Shneor wrote:
> My OS-X app is using ARC, is CoreData Document-Based (using the old
> NSPersistentDocument) and uses 10.9 SDK.
>
> Up until now, I did nothing on my behalf to support user Undo/Redo, still the
> application seemed to work fine. I was very imp
Hi.
My OS-X app is using ARC, is CoreData Document-Based (using the old
NSPersistentDocument) and uses 10.9 SDK.
Up until now, I did nothing on my behalf to support user Undo/Redo, still the
application seemed to work fine. I was very impressed with Cocoa (this
millionth time).
However. In
