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 UICollectio
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 controll
> On Mar 9, 2016, at 18:09 , Daniel Stenmark wrote:
>
> If you’re still having issues, feel free to post up and send us a GitHub link
> to a sample project exhibiting this behavior. Setting up a UICollectionView
> fairly straight-forward; something’s being overlooked here.
Yeah, I think I fo
If you’re still having issues, feel free to post up and send us a GitHub link
to a sample project exhibiting this behavior. Setting up a UICollectionView
fairly straight-forward; something’s being overlooked here.
Dan
> On Mar 9, 2016, at 5:55 PM, Daniel Stenmark wrote:
>
> Did you set the p
Did you set the prototype cell’s Reusability Identifier?
http://i.imgur.com/1uLxYPo.png
Dan
On Mar 9, 2016, at 5:29 PM, Rick Mann
mailto:rm...@latencyzero.com>> wrote:
On Mar 9, 2016, at 16:05 , Daniel Stenmark
mailto:dstenm...@opentable.com>> wrote:
Because I want all the benefits the spec
I did. This is at least the second bug about this I've reported.
Basically, every few years I end up having to do this, and work around the
problem one way or another. I usually write a bug report when I do.
It seems Apple has improved things slightly (e.g., you can actually still build
cells i
Write a bug like I did saying how difficult it is using Interface Builder to
construct the UI you desire. Give as concrete an example as you can, and if
you've seen an Apple app do similar, mention it. If you've seen a third party
app do it, mention it, too. Sometimes you'll get some free tech s
> On Mar 9, 2016, at 16:05 , Daniel Stenmark wrote:
>
>> Because I want all the benefits the specific view controller gives me,
>> namely the ability to build the cells right in the view.
>
> What’re you talking about? You can still build custom UICollectionView cells
> right into the view w
> On Mar 9, 2016, at 17:13 , Gary L. Wade wrote:
>
> If you can require iOS 9, pinning appears to be supported. If earlier, you
> might be able to do what you want by overriding a layout class. I haven't
> tried it myself, though. I know your pain with respect to a
> UITabBarController, thoug
If you can require iOS 9, pinning appears to be supported. If earlier, you
might be able to do what you want by overriding a layout class. I haven't tried
it myself, though. I know your pain with respect to a UITabBarController,
though, but that was easy to re-enclose in another view, although I
> On Mar 9, 2016, at 17:05 , Gary L. Wade wrote:
>
> I'm not sure exactly about your layout, but maybe what you want are
> supplementary views?
Supplementary views scroll with the content. I want non-scrolling views.
> --
> Gary L. Wade (Sent from my iPhone)
> http://www.garywade.com/
>
>> O
I'm not sure exactly about your layout, but maybe what you want are
supplementary views?
--
Gary L. Wade (Sent from my iPhone)
http://www.garywade.com/
> On Mar 9, 2016, at 3:04 PM, Rick Mann wrote:
>
> There's a severe weakness in Storyboards for which I'm hoping a better
> solution exists.
>
> On Mar 9, 2016, at 16:05 , Daniel Stenmark wrote:
>
>> Because I want all the benefits the specific view controller gives me,
>> namely the ability to build the cells right in the view.
>
> What’re you talking about? You can still build custom UICollectionView cells
> right into the view w
> On Mar 9, 2016, at 16:05 , Daniel Stenmark wrote:
>
>> Because I want all the benefits the specific view controller gives me,
>> namely the ability to build the cells right in the view.
>
> What’re you talking about? You can still build custom UICollectionView cells
> right into the view w
> Because I want all the benefits the specific view controller gives me, namely
> the ability to build the cells right in the view.
What’re you talking about? You can still build custom UICollectionView cells
right into the view when using a plain old UIViewController.
Dan
___
Because I want all the benefits the specific view controller gives me, namely
the ability to build the cells right in the view.
I guess I have to give up on that. One small silver lining is I can break those
into NIBs and not duplicate them (I have three different collection views that
all reus
Why are you locking yourself into a heavily customized
UICollectionViewController? Why not just use a generic UIViewController and
hook up your view elements the old fashioned way?
Dan
> On Mar 9, 2016, at 3:04 PM, Rick Mann wrote:
>
> There's a severe weakness in Storyboards for which I'm h
I might be misunderstanding, but why not just use a regular UIViewController
scene, throw a collection view in it, throw your other view into it too, and
then conform to UICollectionViewDataSource and -Delegate “manually”?
It’s a few more outlets to connect by hand but isn’t UICollectionViewCont
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 UINavigation
19 matches
Mail list logo
