Re: CATiledLayer requesting tiles that are way out of view bounds
Re: CATiledLayer requesting tiles that are way out of view bounds
- Subject: Re: CATiledLayer requesting tiles that are way out of view bounds
- From: Kyle Sluder <email@hidden>
- Date: Thu, 11 Jul 2013 14:15:10 -0700
On Thu, Jul 11, 2013, at 01:49 PM, Steve Mills wrote:
> On Jul 11, 2013, at 14:25:08, Kyle Sluder <email@hidden> wrote:
>
> > If the coordinates it's asking for are valid within your document view,
> > what's the issue? They might be necessary for correctly drawing or
> > animating your view.
>
> It's not animating.
Layers animate by default, even if the animation has zero duration.
Things have gotten better recently with the advent of
NSAnimationContext.allowsImplicitAnimation.
> Plus, those areas were already drawn, so they should
> be cached. Because of our *extremely* complex drawing system, it causes
> problems.
Under the Cocoa drawing architecture, any part of your view can be
invalidated at any time for any reason. Caching complex drawing has
always been your responsibility.
If we think about the time before layers, you would probably create an
offscreen bitmap context for your rendering and blit the relevant
portions to the screen in -drawRect:.
With layers, you have some more flexibility, but only if you take the
reins away from Cocoa's automatic layer-backing.
--Kyle Sluder
_______________________________________________
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