Mailing Lists: Apple Mailing Lists
 Image of Mac OS face in stamp
Re: Binding to Accessors of Application Delegate
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Binding to Accessors of Application Delegate


On May 18, 2006, at 9:01 AM, Christopher Hickman wrote:
Okay, I guess I just assumed at some point along the way that invocations
targeting NSApp where NSApp doesn't respond to that selector were
automatically forwarded to NSApp's delegate

They're not. You're confusing this with the responder chain:
<http://developer.apple.com/documentation/Cocoa/Conceptual/ BasicEventHandling/Concepts/AboutRespChain.html>

I have a model object that is my application's delegate. I
want to bind to accessors of said model object, and I tried to do that by
binding to File's Owner (NSApplication) with the model key path of
someAccessor. NSApp doesn't implement someAccessor, but its delegate does.
However, at runtime my NSTextField whose value is bound to File's Owner's
someAccessor shows "Not Applicable" instead of the NSString returned by
someAccessor. I don't get a runtime error, so I checked gdb and found that
my accessor is never called. Am I doing this wrong?

Why not just bind to [NSApp].delegate.someAccessor?

mmalc

_______________________________________________
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







References: 


 >Binding to Accessors of Application Delegate (From: "Christopher Hickman" <email@hidden>)























Visit the Apple Store online or at retail locations.

1-800-MY-APPLE


Contact Apple | Terms of Use | Privacy Policy


Copyright © 2011 Apple Inc. All rights reserved.