Re: Synchronized outlets and actions
Re: Synchronized outlets and actions
- Subject: Re: Synchronized outlets and actions
- From: Dan Price <email@hidden>
- Date: Thu, 5 Jan 2006 17:12:37 +0000 (GMT)
--- Jonathon Mah <email@hidden> wrote:
> So, bindings are what you want. When I first tried
> it out, I was
> confused as hell. (And, it seems, so were many many
> others.) But
> after a short time it will just "click", and you'll
> wonder how you
> ever lived without them. One fallacy common to
> binding newbies: You
> _do not_ bind, say, the text field to both the model
> and the slider.
> Rather, you bind both the text field and the slider
> to the model
> object -- the text field shouldn't and doesn't need
> to know that
> there's a slider representing the same value, and
> vice-versa.
I don't think it will be as simple as that. For one
thing, many of these properties are stored in C++
classes (my app's core is C++, with ObjC wrappers and
glue code). For another, these controls are in
palettes in seperates nibs from the NSApplication
delegate.
They're currently handled by the palettes'
NSWindowController delegate - it accesses the app
delegate from the NSApplication object, and then
accesses that to get the document object containing
the model. It's all done in code, and isn't as elegant
as I would like. How on earth could I do that with
bindings?
Can someone point me to a good doc on bindings? One
which goes beyond the single-window application
example. Any implementation must be compatible with
10.3 and I'm not using Core Data either.
Cheers.
___________________________________________________________
Yahoo! Photos NEW, now offering a quality print service from just 8p a photo http://uk.photos.yahoo.com
_______________________________________________
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