> On Sep 22, 2015, at 4:51 PM, Jim Thomason wrote:
>
> My request was specifically about keeping two NSArrayControllers in sync that
> are -not- bound to a content array.
Connect the first array controller to the managed object context. Bind the
second array controller to the content of the f
My request was specifically about keeping two NSArrayControllers in sync
that are -not- bound to a content array.
The case I was tooling around with was for a root level object that just
fetches all of its data automatically and bypasses any contentArray binding.
Hypothetically, you could have wh
> On Sep 22, 2015, at 7:40 AM, Jim Thomason wrote:
>
> The question is simple - is there a reasonable way to create two
> NSArrayControllers, have them bound to an entity through CoreData, and keep
> them in sync?
One way would be to bind the two array controllers to the same content array.
Th
> Array Controllers etc. can be configured to monitor their context for
changes and automatically re-fetch when needed. So they should keep in sync
that way without any extra work.
>
It can? How?
I'm only aware of the prepares content flag, but that'll only load the data
into the controller when
> On 22 Sep 2015, at 14:40, Jim Thomason wrote:
>
> First, to be clear, I'm not actually trying to do this. I'm just curious
> how it could be done. I cooked it up while working on other things.
>
> The question is simple - is there a reasonable way to create two
> NSArrayControllers, have them
First, to be clear, I'm not actually trying to do this. I'm just curious
how it could be done. I cooked it up while working on other things.
The question is simple - is there a reasonable way to create two
NSArrayControllers, have them bound to an entity through CoreData, and keep
them in sync?
S
