On 12.12.2009, at 00:54, Graham Cox wrote:
>
> On 11/12/2009, at 9:35 PM, Christian Ziegler wrote:
>
>>> The target controller should be the controller with these outlets. It's OK
>>> to have multiple tiers of controllers, but make sure each one has a clearly
>>> defined role. Sounds like you
On 11/12/2009, at 9:35 PM, Christian Ziegler wrote:
>> The target controller should be the controller with these outlets. It's OK
>> to have multiple tiers of controllers, but make sure each one has a clearly
>> defined role. Sounds like you have not defined a clear role for each
>> controller
On 10.12.2009, at 13:26, Graham Cox wrote:
>
> On 10/12/2009, at 10:45 PM, Christian Ziegler wrote:
>
>> In the target controller I don't have IBOutlets for those steppers and
>> textfields. Those are in another (mediating) controller. Question is whether
>> there is another way to do this in
On 10/12/2009, at 11:26 PM, Graham Cox wrote:
> In general I've found it's a false economy to avoid outlets for all controls
> - you'll want them sooner or later so may as well give everything an outlet
> just as a matter of habit.
I should qualify that - if you end up using bindings you don't
On 10/12/2009, at 10:45 PM, Christian Ziegler wrote:
> In the target controller I don't have IBOutlets for those steppers and
> textfields. Those are in another (mediating) controller. Question is whether
> there is another way to do this instead of defining outlets also in the
> target contro
I think mmalc got me right. Sorry again for my initial mail which was a little
confusing. When I wrote the mail I confused Cocoa Bindings with target/action,
because what I've been doing is, I just connected the selector of one view
TextField) to the takeIntegerFrom IBAction of another one (Ste
On Dec 9, 2009, at 5:47 am, Christian Ziegler wrote:
> Sorry I got to correct myself, it's not Cocoa Bindings, but direct
> target/action. So I connected the takeIntegerValue action of both views to
> each other in contrast to connecting it to a controller.
>
Don't do that.
Both should invoke
On Dec 9, 2009, at 05:47, Christian Ziegler wrote:
> Sorry I got to correct myself, it's not Cocoa Bindings, but direct
> target/action. So I connected the takeIntegerValue action of both views to
> each other in contrast to connecting it to a controller.
>
>
> On 09.12.2009, at 14:26, Christi
Sorry I got to correct myself, it's not Cocoa Bindings, but direct
target/action. So I connected the takeIntegerValue action of both views to each
other in contrast to connecting it to a controller.
On 09.12.2009, at 14:26, Christian Ziegler wrote:
> Hi all!
>
> I got a NSTextView and an NSSt
