Re: Some kind of view "reference" list
Re: Some kind of view "reference" list
- Subject: Re: Some kind of view "reference" list
- From: Daniel Jalkut <email@hidden>
- Date: Wed, 15 Mar 2006 09:58:45 -0500
Most of these views should offer some mechanism of notifying your
delegate class that things have changed (e.g. a "didChange" note or a
target/action message). Why not just have your delegate be in charge
of "pairing" the views in question. Keep a list of views in the box
and map them to views elsewhere. Whenever you get a change
notification in your delegate you can perform your magic. This seems
vastly preferable to building in knowledge of peers to the view itself.
Daniel
On Mar 13, 2006, at 5:48 PM, Mike Abdullah wrote:
In my app's window I have a box that changes its content view based
upon the users choice elsewhere in the interface. This works nicely.
What I ideally would like though, is for if the user changes the
content of this box whilst they are editing one of its fields, the
first responder would switch to the "equivalent" field in the new
content view.
Does anyone know of a reasonably tidy way of achieving this? I
thought about subclassing all the controls of the view so they have
an IBOutlet called something like "equivalent view" and hooking
things up that way, but it seems rather messy. Similarly, to go
through all the controls of the view in code and checking to see if
it has an equivalent seems awkward.
_______________________________________________
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