On Jul 26, 2013, at 5:11 PM, Kyle Sluder <[email protected]> wrote: > On Fri, Jul 26, 2013, at 03:41 AM, Uli Kusterer wrote: >> On Jul 25, 2013, at 20:26, Andreas Mayer <[email protected]> wrote: >>> Am 25.07.2013 um 19:36 schrieb Uli Kusterer <[email protected]>: >>> >>>> Have you considered using a display link callback instead of a timer? >>> >>> Yes. Moving to the display link callback was when I noticed the issue in >>> the first place. >> >> Usually, when drawing from the display link callback is out of sync, it >> simply means you’re taking too long to draw. Optimize your drawing code. >> >>> Calling -setNeedsDisplay: in the display link callback is too fast. It >>> gives smooth animation but leads to timers piling up in the system. > > Or do your drawing offscreen and use the display link to blit it to the > screen.
Yes, that'd work, too, as long as you have spare cycles somewhere else that you can use to parallelise the drawing (e.g. another CPU to run a second thread on). But you have to be able to produce a new frame every 1/60th of a second if you want to draw at 60fps. If DisplayLink notices you can't do that, it will call you less often automatically. Cheers, -- Uli Kusterer "The Witnesses of TeachText are everywhere..." http://www.zathras.de _______________________________________________ Cocoa-dev mailing list ([email protected]) 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: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to [email protected]
