• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Subclass UIScrollView or compose?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Subclass UIScrollView or compose?


  • Subject: Subclass UIScrollView or compose?
  • From: Rick Mann <email@hidden>
  • Date: Thu, 1 Jul 2010 15:29:03 -0700

I'm developing a custom scrolling view, and I could either subclass UIScrollView, or subclass UIView and drop it into a UIScrollView in IB. I prefer the former approach, because it's more straightforward when using the view (which we use in many places).

However, the only way to update the view is to either become the scroll view's delegate, or override the contentSize property setter, and call setNeedsDisplay. Neither of these solutions seems very elegant or obvious.

And just for reference, UITableView subclasses UIScrollView, and doesn't make itself the delegate (at least, it doesn't declare the protocol in the header).

Is there a smarter way to do this?

TIA,
Rick

_______________________________________________

Cocoa-dev mailing list (email@hidden)

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:

This email sent to email@hidden

  • Follow-Ups:
    • Re: Subclass UIScrollView or compose?
      • From: Luke the Hiesterman <email@hidden>
  • Prev by Date: Does a Core Animation Runtime Player/Editor exist?
  • Next by Date: Re: Subclass UIScrollView or compose?
  • Previous by thread: Does a Core Animation Runtime Player/Editor exist?
  • Next by thread: Re: Subclass UIScrollView or compose?
  • Index(es):
    • Date
    • Thread