Re: Forcing a pre-render/cache of a view
Re: Forcing a pre-render/cache of a view
- Subject: Re: Forcing a pre-render/cache of a view
- From: Chuck Pisula <email@hidden>
- Date: Mon, 24 Sep 2001 11:21:04 -0700
To be sure, you should sample your application to see where your time is
being spent, but I would guess the slow speed is not just the rendering.
If you are using a "lazy" browser, data won't be loaded until it has to
be displayed for the "first time", therefore you might want to
concentrate the code that does the loading of data into the browser.
Maybe this is the bottleneck?
Definitely sample though... who knows maybe it is slow the first time
you hit a bunch of new fonts?
-chuck
On Thursday, September 20, 2001, at 07:08 PM, Erik M. Buck wrote:
You can render any view into a bitmap.
You might consider -dataWithPDFInsideRect: to cache the PDF needed to
draw a
view and indirectly force all fonts used to be cached.
----- Original Message -----
From: "Charles Jolley" <email@hidden>
To: <email@hidden>
Sent: Thursday, September 20, 2001 6:56 PM
Subject: Forcing a pre-render/cache of a view
Greetings,
I have a browser that contains a large number of items, each in a
different font. As a result, the first time a user scrolls through
this
list, the performance is pretty poor as each item has to be rendered
into the view.
Does anyone know if there is a way to force the browser (or any view)
to
"pre-render", or cache, itself to speed up future display?
Thanks for any insight!
Cheers,
-Charles
_______________________________________________
cocoa-dev mailing list
email@hidden
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
_______________________________________________
cocoa-dev mailing list
email@hidden
http://www.lists.apple.com/mailman/listinfo/cocoa-dev