• 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
Re: Subclass UIScrollView or compose?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Subclass UIScrollView or compose?


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

I don't use a UIViewController. That is in this case, the view controllers will be provided by others who just want to use my view. Currently my view has properties that must be set for displaying data, but I may switch that to use a data source model like UITableView.

I know it's no problem to drop a view into a UIScrollView. I want to avoid that, and I'm simply looking for the best way for my UIScrollView subclass to actually get updates as its scrolled.

If it's really not good to subclass UIScrollView, why does UITableView do so?

TIA,
Rick

On Jul 1, 2010, at 15:36:21, Luke the Hiesterman wrote:

> If you use a UIViewController, then dropping your custom view into UIScrollView in IB should be completely straightforward for all your uses.
>
> Luke
>
> On Jul 1, 2010, at 3:29 PM, Rick Mann wrote:
>
>> 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
>

_______________________________________________

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>
References: 
 >Subclass UIScrollView or compose? (From: Rick Mann <email@hidden>)
 >Re: Subclass UIScrollView or compose? (From: Luke the Hiesterman <email@hidden>)

  • Prev by Date: Core Data : Save As : Object temporarily missing in fetch results
  • Next by Date: Re: Subclass UIScrollView or compose?
  • Previous by thread: Re: Subclass UIScrollView or compose?
  • Next by thread: Re: Subclass UIScrollView or compose?
  • Index(es):
    • Date
    • Thread