On Nov 20, 2009, at 14:02, Chase Meadors wrote:
> Thought I'd give the question another try. Any insight appreciated.
A while back, I wondered about the same thing, and found two things, both
relatively minor:
1. NSObjectController responds to 'commitEditing:' by committing all the
"editors" t
On Nov 20, 2009, at 2:02 PM, Chase Meadors wrote:
>
> Thought I'd give the question another try. Any insight appreciated.
May I suggest you invest in a book called Cocoa Design Patterns, where that
**exact** question is painstakingly
answered.___
Thought I'd give the question another try. Any insight appreciated.
On Nov 18, 2009, at 7:44 PM, Chase Meadors wrote:
I wanted to add that my problem in the second part of my question
has been solved. The only reason it wasn't working was that
graphView is actually a CALayer, and doesn't au
On 19/11/2009, at 11:44 AM, Chase Meadors wrote:
> However, my question becomes more strange, as now I have many working
> bindings systems in my code without any NSControllers. Binding to plain old
> NSObjects seems to be fine. What is the purpose of NSController?
NSObjectController and frie
I wanted to add that my problem in the second part of my question has
been solved. The only reason it wasn't working was that graphView is
actually a CALayer, and doesn't automatically call -willChange and -
didChange. Doing that solves the issue.
However, my question becomes more strange, a
Maybe I'm missing some things here, but hey; that's what I come to the
list for.
I'm not fully understanding the need for NSController's and/or what
they do.
Say I have an NSObject subclass:
(.h)
@interface TestObject : NSObject {
BOOL boolProp;
}
@property BOOL boolProp;
