Re: Cocoa Binding Musings
Re: Cocoa Binding Musings
- Subject: Re: Cocoa Binding Musings
- From: Scott Anguish <email@hidden>
- Date: Tue, 11 May 2004 01:14:59 -0400
On May 10, 2004, at 4:26 PM, mmalcolm crawford wrote:
4) If File's Owner in IB is set to NSApplication, and the delegate is
connected to a class that supports KVC, the delegate never gets passed
get/set invocations.
I'm not sure why you think it should?
Oh, I can see the potential use there. It could be an expected
behavior that the delegate get an option at a message sent to an object
if it doesn't handle it.
Obviously, you can work around this by creating a
separate NIB with File's Owner set to your class (alleviating the
need to
have a delegate), but it's a pain for small applications. It seems
like the
delegate should be able to handle the KVC on behalf of NSApplication.
Am I
missing something, or is this a bug?
I think you're missing the point of KVC. And overlooking keypaths;
you can still bind to:
[File's Owner].delegate.whatever
Sigh.. stupid that I missed that option
5) Text fields only update user defaults after the user has pressed
the
enter key. (It's possible that this is true for other controls -- I
think
I've seen this behavior in table cells.)
This seems like a bug from a HIG point-of-view -- if a user types
"abc" into
a text field and then closes the application, the fact that they
typed "abc"
is never recorded in the user defaults.
This should be handled automatically by the NSEditor and
NSEditorRegistration protocols.
Yes, however there is a bug where if the window closes with
uncommitted changes in a textfield on a non-document window that you
can loose the contents. you need to manually send the commit to the
data model.
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.