Am 25.07.2013 um 19:36 schrieb Uli Kusterer <witness.of.teacht...@gmx.net>:
> 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. Calling -setNeedsDisplay: in the display link callback is too fast. It gives smooth animation but leads to timers piling up in the system. Since I can use Core Animation, that is obviously the better solution. It also makes my application look less power hungry - because now it is the WindowServer doing the drawing and eating cpu. ;) Andreas _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) 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 arch...@mail-archive.com
