On Nov 12, 2012, at 7:30 , Fritz Anderson <[email protected]> wrote:
> The whole point of a UITableViewController is to have a controller that > autonomously instantiates a table view as its root view. Interface Builder > isn't making an arbitrary choice; the controller, not IB, creates the view. Actually, I disagree. IB is still creating the view. It's clearly present in the storyboard, and if you remove it, you don't get the view. > If you want a UITableView to be a sibling of other views, instantiate a > UIViewController subclass, make its .view a plain UIView (or as the problem > demands), drop in the table view along with sibling views, and connect the > table to an outlet in the controller. You won't get a template with the > delegate and data source methods prefilled, but there's nothing magic about > it. Just put UITableViewController.h into the Assistant editor and paste the > declarations into your controller's implementation. Unfortunately, if you do this, you don't get any of the built-in support for creating static table view cells in IB (nor can you build dynamic cells). For that matter, you really aren't able to have multiple table views in a window and take advantage of directly editing them in IB. -- Rick _______________________________________________ Cocoa-dev mailing list ([email protected]) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to [email protected]
