On 11/12/2009, at 8:59 PM, Alastair Houghton wrote:
> Anyway, the thing to do is to draw what you want, and then *if* it's going
> too slowly there are various things you can do to speed it up (like caching
> any expensive rendering in an NSImage, doing reduced or simplified rendering
> during
On 11 Dec 2009, at 10:35, Michael Abendroth wrote:
> Woah, thanks a lot, Alastair! The reason I asked was because e.g.
> NSTextFieldCell subclasses get drawn & redrawn quite a lot, so on
> slower systems this might have been a problem ...
If you were e.g. rendering something huge with an NSShadow
On Fri, Dec 11, 2009 at 11:14 AM, Alastair Houghton wrote:
> On 11 Dec 2009, at 09:10, Michael Abendroth wrote:
>
>> when drawing custom buttons, should you use NSBezierPath or NSImage
>> instances?
>
> Yes.
>
>> Which is more efficient, performance-wise / memory-wise?
>
> You probably don't need
On 11 Dec 2009, at 09:10, Michael Abendroth wrote:
> when drawing custom buttons, should you use NSBezierPath or NSImage instances?
Yes.
> Which is more efficient, performance-wise / memory-wise?
You probably don't need to worry too much about this on modern systems. In
fact, I'll go further
Hi,
when drawing custom buttons, should you use NSBezierPath or NSImage instances?
Which is more efficient, performance-wise / memory-wise?
Thanks for any tips,
- Mike
___
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post admin re
