Figured I'd address all the comments inline in one batch, and then
point out what I came up with. An almost viable solution is up top for
reference purposes, and a seemingly better one is towards the bottom.
Hm, do operations using primitive accessors also get registered on the undo
stack? If
I've got a CoreData document based application, and I'm trying to undo
my object creation in a single step.
Here's the issue - I'm storing an ordered index on my entities so I
can keep track of the order of creation. To do this, upon object
creation, I yank out the highest order parameter for my
Jim,
An interesting situation. I do not have anything definitive, but just
some ideas and comments
On Oct 05, 2009, at 09:10, Jim Thomason wrote:
-(void) createOrder {
int highOrderIndex = [self getHighestIndexSomeHow];
[self setValue:[NSNumber numberWithInt:highOrderIndex]
On Oct 5, 2009, at 06:10, Jim Thomason wrote:
I've got a CoreData document based application, and I'm trying to undo
my object creation in a single step.
Here's the issue - I'm storing an ordered index on my entities so I
can keep track of the order of creation. To do this, upon object
On 5 Oct 2009, at 8:10 AM, Jim Thomason wrote:
-(void) awakeFromInsert {
[super awakeFromInsert];
[self performSelector:@selector(createOrder:) withObject:nil
afterDelay:0];
}
-(void) createOrder {
int highOrderIndex = [self getHighestIndexSomeHow];
[self setValue:[NSNumber
On 2009 Oct 05, at 06:10, Jim Thomason wrote:
But the problem is, if the user undoes the creation of a new object,
two undos are required
Welcome to what I call Core Data Undodoodoo :)
How can I deal with this? I've been trying various combinations of
begin/endUndoGrouping,
The
