On Sep 24, 2013, at 17:14 , Fritz Anderson <fri...@manoverboard.org> wrote:
> Put an identifier on the embed segue, and listen for it in the parent > controller's prepareForSegue:sender:. The segue that comes into the method > will get you the contained controller. Ah, that's how to get at it. > I'm surprised it's subclassable; my memory was that it wasn't, and I beat up > on a junior programmer for doing it. But he was using the page-view > controller as its own data source, and besides he needed a beating on general > principles. It's subclassable in the same way UITableViewController is subclassable, and I think it makes a lot of sense for it to be its own datasource and delegate, just like a UITableViewController is usually for a UITableView. Perhaps there should be a UIPageView to make the analogy more complete. The problem I have is that I have to create the thing programmatically to make it useful. But a more capable IB would let me do this all in IB. One thing it would need to support is wiring IBOutlets across scenes. There can also be a distinction between static and dynamic page view content (in which case the static content could be entirely specified in IB, and dynamic view controller template scenes could be specified). -- Rick _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) 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 arch...@mail-archive.com
