Re: Scroller With CATiledLayer Running out of Memory
Re: Scroller With CATiledLayer Running out of Memory
- Subject: Re: Scroller With CATiledLayer Running out of Memory
- From: Gordon Apple <email@hidden>
- Date: Sat, 07 Aug 2010 13:51:35 -0500
- Thread-topic: Scroller With CATiledLayer Running out of Memory
So, are you saying that the backing layer will always be the size of the
view? Or that there there will always be enough tiles to cover the view?
If that is the case, then it sounds like what you are advocating is to
create my own scroller or somehow tie the scroller to another (overlaid)
view with a fixed frame but scrollable bounds, so that it only creates tiles
(or a single CALayer) needed to display within its frame?
On 8/7/10 12:57 PM, "David Duncan" <email@hidden> wrote:
> On Aug 6, 2010, at 6:07 PM, Gordon Apple wrote:
>
>> I thought that was what the scroller was supposed to do for you, at least if
>> you actually optimized drawing to use the "rect" in drawRect, which is what
>> I am currently trying to do.
>
>
> That's how it works on AppKit in non-layer backed mode. In UIKit and in AppKit
> under layer backed mode however a layer will retain backing store for its
> entire content area (generally bounds.size * contentsScale). You can ask for
> partial draws, but if the content isn't going to change then that may not be
> worth it.
> --
> David Duncan
>
_______________________________________________
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