Skip to content

Conversation

@aout
Copy link

@aout aout commented Feb 7, 2014

Any subclass would override the content view, leaving the custom scroll view with a nil ptr.
I guess this is less flexible but we could even nest the custom scroll view inside the cell itself to make it opaque for the end user.

@ashfurrow
Copy link
Contributor

Yeah, I don't know. What about having the property is bad? I mean, I don't like to rely on the view hierarchy implicitly.

@aout
Copy link
Author

aout commented Feb 7, 2014

I think it's just a matter of situation. I didn't find any solution with a subclass and multiple XiBs for quick prototyping.
I wanted to keep the code very neat and defer all the work to the IB. This way I can design my "front" view and my "back" view (I tweaked it a bit too) knowing I don't have anything to do but plug the IBOutlets.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants