>> So if one does not care about zooming and all other things UIScrollView >> helps with... this is not a terribly wrong thing to do? It's just that there >> is something in UIKit that does this, too? After all -in a very simple >> setup, think user interaction disabled- changing the frame of a subview vs >> changing the content offset of UIScrollView is not that much different. I am >> just wondering what's going on "under the hood" and if the UIScrollView has >> just some more tricks why it should be use instead. > > From a performance POV, it is highly unlikely that you will ever notice a > difference between UIScrollView and your own implementation. It is really > primarily just in the user experience. I suppose if you decide that there is > no user interaction then the difference is basically moot. You may find the > UIScrollView model easier to manage – YMMV – but if there is a chance that > this non-interactive view could become interactive, I would just go with with > UIScrollView and not look back.
Awesome. That's exactly the information I was after. Thanks a lot! cheers, Torsten _______________________________________________ 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: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
