Daniel,
Each NSOperation is, conceptually, its own thread. In addition to
using NSInvocationOperation to easily dispatch a work function to an
object, you'll also need to follow the multi-threading rules
described in the Core Data Programming Guide.
--
-Ben
_
Oh, sorry, I meant dependent not independent!
Using NSInvocationOperation looks as though it would work fine
assuming that none of my calculations had any dependencies, which is
not always true. I'm currently working on a system that uses
NSOperation objects as delegates for NSManagedObjec
On Mar 28, 2008, at 22:56, Daniel Thorpe wrote:
Oooh, that might work...
But how do you assign independent operations using
NSInvocationOperation objects?
I don't understand the question. Each NSInvocationOperation represents
the independent execution of a method on an object in a thread
Oooh, that might work...
But how do you assign independent operations using
NSInvocationOperation objects?
On 28 Mar 2008, at 19:49, Quincey Morris wrote:
On Mar 28, 2008, at 12:09, Daniel Thorpe wrote:
I want to store the objects using Core Data, but have come up with
a possible proble
On Mar 28, 2008, at 12:09, Daniel Thorpe wrote:
I want to store the objects using Core Data, but have come up with a
possible problem. I've not used Core Data before, so I may have
understood this incorrectly, but the entities must be subclasses of
NSManagedObject, which NSOperation is not
Hello everyone, I'm a bit of a Core Data newbie, so any thoughts on
this would be much appreciated...
I have some objects, where each performs calculations, so I've
subclassed NSOperation so that I can configure their dependencies and
execute them on an NSOperationQueue.
I want to store t
