On Aug 1, 2009, at 07:03, Richard Somers wrote:
It is an inspector panel. One panel for many documents.
This is a crucial piece of information which changes the nature of the
problem to be solved. You gotta tell us the relevant information up
front. :)
If I create the inspector panel in
On Aug 1, 2009, at 8:03 AM, Richard Somers wrote:
The error message "Cannot perform operation without a managed object
context" indicates the binding is not working.
Upon further investigation I have discovered that my window controller
-document method returns nil. So as far as the binding
On Aug 1, 2009, at 8:03 AM, Richard Somers wrote:
How do you debug a binding?
Troubleshooting Cocoa Bindings
http://developer.apple.com/documentation/Cocoa/Conceptual/CocoaBindings/Concepts/Troubleshooting.html
Richard
___
Cocoa-dev mailing list
On Aug 1, 2009, at 12:28 AM, Quincey Morris wrote:
You haven't said what you mean by an "auxiliary panel".
It is an inspector panel. One panel for many documents. The panel is
made visible with a menu selection which by the way currently works.
Or, in all 3 cases, just pass the managed obj
The below is incorrect. Key-Value Coding (and therefore Key-Value
Observing and bindings) will always use a method if one is present.
-- Chris
On Jul 31, 2009, at 8:33 PM, Kyle Sluder wrote:
Because you have a managedObjectContext ivar, you never change its
value so it defaults to nil, a
On Jul 31, 2009, at 20:03, Richard Somers wrote:
I am having problems binding an auxiliary panel with the document's
managed object context. The panel is in nib separate from the
document nib. My code looks like this.
@interface AuxPanelController : NSWindowController
{
@private
NSManage
Because you have a managedObjectContext ivar, you never change its
value so it defaults to nil, and +[NSObject(NSKeyValueCoding)
accessInstanceVariablesDirectly] returns YES, -[AuxPanelController
objectForKey:@"managedObjectContext"] will always return nil. Ditch
the ivar.
Need to corr
On Jul 31, 2009, at 9:58 PM, Richard Somers
wrote:
My code here came out of Hillegass Third Edition Chapter 12. I will
need to think about this.
Doesn't matter; you must be prepared for super's initializer to return
a different object (with the possible exception of -[NSObject init],
b
On Jul 31, 2009, at 9:33 PM, Kyle Sluder wrote:
Unrelated note: you need to assign self = [super initWithWindowName:
…].
My code here came out of Hillegass Third Edition Chapter 12. I will
need to think about this.
Because you have a managedObjectContext ivar, you never change its
value
On Jul 31, 2009, at 8:03 PM, Richard Somers
wrote:
@interface AuxPanelController : NSWindowController
{
@private
NSManagedObjectContext *managedObjectContext;
}
@implementation AuxPanelController
- (id)init
{
if (![super initWithWindowNibName:@"AuxPanel"])
Unrelated note: you need t
10 matches
Mail list logo