Re: Drawing optimization question

[Nicolas Roard]

Le 9 mars 05, à 17:15, Adrian Robert a écrit :

> Hi,
>
> I'm drawing directly to a view, either using [NSString -drawAtPoint..] 
> or,
> say, with NSRectFill() and friends.

In addition to what you describe (flush problem?), NSString 
-drawAtPoint: has apparently a huge resource load, as each time you 
instanciate a layout manager, etc.
Plus the cache size in NSStringDrawing is imho too small (we did some 
profiling with quentin during the fosdem using Shark, on a tableview 
containing lots of lines/columns, and with the current values, we had a 
50% hit miss with NUM_CACHE_ENTRIES=16).
I'm not sure why we care about the layout manager for NSStringDrawing 
-- it seems to me that you don't really want/need to bother with one in 
general if you're using thoses methods..

--
Nicolas Roard
"Any sufficiently advanced technology is indistinguishable from magic."
 -Arthur C. Clarke