CODEWITHSUNDEEP
iphoneobjective-ccocoa-touchuikit
Fin
Fin

Reputation: 131

How does UIView nextResponder know what the UIViewController is?

Just as a matter of curiosity, how does the nextResponder method implementation of the UIView class know who is the UIViewController that manages the view? The UIResponder documentation states this, and I can see it work, but I don't quite understand it. To the best of my knowledge, a UIView does not maintain a reference to it's controller, so what's happening behind the scenes? Or am I just missing something obvious?

I'm still very new to Objective-C and iPhone development so I apologize if this is something obvious, but I am quite curious.

Thanks!

Upvotes: 13

Views: 6152

Answers (4)

drunknbass
drunknbass

Reputation: 1672

there is actually a private api on uiview to get the uiviewcontroller it belongs to. Very handy ;) My guess is when a view is added to a view controller(controller.view) this property is set.

Upvotes: 1

Kevlar
Kevlar

Reputation: 8924

If you look at UIView.h, you can see a member variable named _viewDelegate that is of type UIViewController*, this is probably where the view controller reference is stored when the viewcontroller's view property is set, and where it knows to look when you call nextResponder.

Upvotes: 2

Shivaraj Tenginakai
Shivaraj Tenginakai

Reputation: 41

My guess is that the system may maintain a mapping between UIViewController objects and their root UIView objects. The code for traversal of responder chain may use this mapping to pass the event to the corresponding UIViewController object.

Typically subviews are added using:

subview = [viewController view]

[superview addSubview subview]

addSubview method automatically sets superview as the next responder for subview, so:

a) viewController wont have the opportunity to insert itself between superview and subview.

b) viewController does not know about superview, hence it cannot set it as its next responder.

c) Apple recommends that a view may not be shared across controllers. In absence of multi-threading this restriction makes sense only if there is a map of views and view controllers.

Upvotes: 0

Darren
Darren

Reputation: 25619

The responder chain is separate from the view hierarchy. The responder chain might look like this: 

First Responder > View Hierarchy > Window > Window Delegate > etc...

However, objects can insert themselves into the responder chain and that's what UIViewController does. From the docs:

Because view controllers are tightly bound to the views they manage, they are also part of the responder chain used to handle events. View controllers are themselves descendants of the UIResponder class and are inserted into the responder chain between the managed view and its superview.

In Big Cocoa, this is accomplished using the -setNextResponder: method. That method isn't public in Cocoa Touch, but nevertheless that's what UIViewController appears to do.

Upvotes: 8

Related Questions