Re: Core Data: undo and non-object attribute [SOLVED]
Re: Core Data: undo and non-object attribute [SOLVED]
- Subject: Re: Core Data: undo and non-object attribute [SOLVED]
- From: Matteo Rossi <email@hidden>
- Date: Sun, 15 Oct 2006 19:09:53 +0200
First of all, thank you, Jacob: you solved my problem and made me
clearly see what I was doing wrong.
By implementing primitiveX, primitiveY, I was able to support undo.
Congratulations for your simple but very effetive explanations: it's
always a pleasure to find someone like you.
Why do you need to keep x and y in a struct instance variable?
That's the hardest part of the problem. I'll try to explain. My
drawing application needs to handle many graphic objects (say
10.000). Since I'm using OpenGL and find myself refreshing the
drawing view many times per second during panning and zooming I want
to store object coordinates in ivars because I suspect that using
valueForKey: would be a total waste of time. Yes I know CD is "highly
optimized and continuously improved to be efficient" but it still
requires much more time than the good old way. Am I wrong ? By
keeping x and y in a struct I can pass them as a double pointer to
opengl functions. I must be sincere: I haven't tested performances in
both cases. It's just an assumption, by now. Thank you again.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden