I really wanted to be able to take advantage of the storyboard editor for many reasons. Turns out, you can (thanks to Daniel Stenmark for cluing me in).
You just can't drop in a UICollectionViewController (this is a lame weakness). But you can put in a UIViewController, and drop in a UICollectionView, and then (once you've wired everything up that doesn't get automatically wired), you can basically use it as if it were a "proper" UICollectionViewController (that is, you can create UICollectionViewCells right in the view, something you didn't used to be able to do). So, now it's all working. > On Mar 9, 2016, at 19:50 , Alex Zavatone <z...@mac.com> wrote: > > Would it help if you created an XIB tor that particular scene? > > If you delete your top level view for that scene in the storyboard, but that > scene is wired to your view controller, your view controller will load that > XIB for the top level view. That XIB also has to be wired to your view > controller. > > Would that have any advantage for you? > > On Mar 9, 2016, at 6:04 PM, Rick Mann wrote: > >> There's a severe weakness in Storyboards for which I'm hoping a better >> solution exists. >> >> When you create a scene for say, a UICollectionView, the Storyboard makes it >> very easy, but it also imposes a severe limitation. In my case, my >> UICollectionViewController subclass lives inside a UINavigationController. >> It manages the controls in the toolbar and the title, as well as the content. >> >> But inevitably I want to add additional views beneath the UINavigationBar >> that are NOT CONTAINED within the UICollectionView (in this case, a >> UISegmentedControl for sorting the contents). The only way I see how to do >> this with Storyboards is to create two view controllers, one that embeds the >> UICollectionViewController subclass. But now its impossible to wire up >> UINavigationBar items to it. I've been forced to split up view control >> across two view controllers that really should be one. >> >> This is solved by having the UICollectionView controller subclass have its >> view property point to a generic containing view, and its collectionView >> property point to the collectionView subview. But it's not really designed >> to work this way, and Storyboards definitely doesn't support this. >> >> The Apple-provided way imposes a HUGE burden. >> >> Is there any happy middle ground? >> >> I've written this bug before, but Apple doesn't care. >> >> -- >> Rick Mann >> rm...@latencyzero.com >> >> >> >> _______________________________________________ >> >> 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/zav%40mac.com >> >> This email sent to z...@mac.com > -- Rick Mann rm...@latencyzero.com _______________________________________________ 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
