Re: There must be a better way

Of course they can. In the view's xib, the "File's Owner" object represents the object that is doing the loading of the xib. In this case, that is your view controller. Sent from my iPhone On Dec 23, 2009, at 16:18, Charlie Dickman <3tothe...@comcast.net> wrote: Except the view and the

Re: There must be a better way

On Wed, Dec 23, 2009 at 1:18 PM, Charlie Dickman <3tothe...@comcast.net> wrote: > Except  the view and the controller are in separate xib's so they can't be > connected in this way. Who/what is the "file owner" of the two xib's you are talking about? Most commonly those are the objects that load

Re: There must be a better way

Except the view and the controller are in separate xib's so they can't be connected in this way. On Dec 23, 2009, at 4:08 PM, Seth Willits wrote: > On Dec 23, 2009, at 11:19 AM, Charlie Dickman wrote: > >> In an iPod Touch/iPhone app where the view is in 1 xib and it's controller >> is in a d

Re: There must be a better way

I am implementing a view to allow the user to select his preferences from within the app while it is running instead of having to exit the app to use the settings app to do so and then restarting my app. The preferences view is controlled by the controller I am trying to define. It knows how to

Re: There must be a better way

On Dec 23, 2009, at 11:19 AM, Charlie Dickman wrote: > In an iPod Touch/iPhone app where the view is in 1 xib and it's controller is > in a different one, according to the view-controller-data paradigm, is there > a better way to link the view to the controller than... Surely the controller is

Re: There must be a better way

Is there a reason why your view so tightly bound to it's controller? Typically you define a protocol for any object to respond to and expose a delegate property to define that type of interface. Examples of this are very common in AppKit and UIKit, such as NS/UITableView or UIImagePickerCon

There must be a better way

In an iPod Touch/iPhone app where the view is in 1 xib and it's controller is in a different one, according to the view-controller-data paradigm, is there a better way to link the view to the controller than [(myView *) [[self view] setController: self] in the controller where "controller" has