All sorted.
Turns out that in my obsession with bindings and coredata I forgot
that to communicate with objects in a NIB you need to use Outlets.
Doh! I've now setup outlets from my datasource to the controllers and
can pull the selection and context out no problems.
Thanks for bearing wi
Fixed that error now. I had a rogue arraycontroller in the NIB file
from a previous predicate exercise. The nib is cleaned up and still no
selection. It appears that I'm unable to get anything other than NULL
from any objects instantiated in the NIB file. My appDelegate holds
the code for t
I'd like to reiterate what Quincey noted:
"BTW, I notice that the "Cannot perform operation without a managed
object context" error is logged *before* you log "default". The
problem is not apparently anything to do with getting the selection in
the code you posted, since it happens before you do t
- (void)getSelectedAccount{
NSString *accountName = @"Bank";
NSLog(accountName);
accountName = [[MLoutlineViewController selection]
valueForKey:@"name"];
NSLog(accountName);
//get managedObjectContext in preparation for fetch code
moc
On 21/05/2008, at 4:01 AM, Jonathan Dann wrote:
In addition:
So, I guess my question is: how is your NSOutlineView populated? Do
you have to NSTableColumn of the NSOutlineView bound to the tree
controllers @"arrangedObjects.name" keypath? If this is the case, in
what way are you giving
In addition:
So, I guess my question is: how is your NSOutlineView populated? Do
you have to NSTableColumn of the NSOutlineView bound to the tree
controllers @"arrangedObjects.name" keypath? If this is the case, in
what way are you giving the tree controller content to work with.
All the
2008-05-19 22:25:46.990 moolahcoredata[664:10b] Cannot perform
operation without a managed object context
I just tried to replicate this and got this error when the tree
controller wasn't bound to the moc and 'prepares content' is
selected. This, of course, would fail as the controller i
On May 20, 2008, at 03:10, Steven Hamilton wrote:
I have an NSOutlineVIew bound to a NSTreeController in entity mode
bound to an entity called "Account" which has a NSString called "name"
So the NSTreeController is set to entity mode and the entity name is
"Account", yes? I re-phrased it l
On 20/05/2008, at 5:18 AM, Jonathan Dann wrote:
On 19 May 2008, at 13:29, Steven Hamilton wrote:
I have a core data master-detail interface that consists of a
sourcelist on the left and a tableview.
The source list displays object from a core data entity. THe table
view will be populate
On Mon, May 19, 2008 at 8:18 PM, Jonathan Dann <[EMAIL PROTECTED]> wrote:
> The way its
> traditionally (and designed to be) used is that the tree controller is the
> outline view's data source.
This statement is a little misleading: the tree controller is designed
to have bindings from the outli
On 19 May 2008, at 13:29, Steven Hamilton wrote:
I have a core data master-detail interface that consists of a
sourcelist on the left and a tableview.
The source list displays object from a core data entity. THe table
view will be populated by a custom datasource as I have to do some
dat
I have a core data master-detail interface that consists of a
sourcelist on the left and a tableview.
The source list displays object from a core data entity. THe table
view will be populated by a custom datasource as I have to do some
data munging on the way from core data to the tableview
12 matches
Mail list logo
