On Dec 9, 2008, at 8:09 PM, Ricky Sharp wrote:
In some cases, other attributes, when set, will 'dirty' that flag
followed by a setNeedsDisplay. Colors will then be re-fetched/
created and then reused until the next change comes along.
Perfectly good example of "timely optimization".
The main reason (which I may not have communicated clearly) is
because any unnecessary work at all is wasteful. Especially for mobile
platforms (laptop and iPhone users will thank you for sparing their
battery life ... or curse you for not caring).
Asking for the shared user defaults instance, then asking it for a
value, then unarchiving a more useful object from it, *then* using it
to draw is certainly more work than caching the value only when it
changes. It's not like it's performance tuning - it's *basic design*.
--
I.S.
_______________________________________________
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:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com
This email sent to [EMAIL PROTECTED]
