On Thu, 13 Nov 2003 at 16:03, Chris Hawks wrote:
> ---Reply to mail from Alan Hoyle about Problem with conversion of page with lots of
> tables.
>
> > Is there any way to speed up the table rendering speed other than chopping
> > the table up into smaller pieces? Are tables inherently 1 bit? I see
> > lots of dithering artifacts....
>
> Tables are chopped up into pieces to get around the PalmOS limitation
> of 64K for images and off screen windows. Tables are rendered at the depth
> proveded by the parser (--bpp=X). Images are also saved at this bit depth.
I only saw 1 BPP on my screen in "fullscreen" mode, but I'm not including
any images....
I've heavily edited the content to make it fit on one page width.
> > As an aside: why aren't tables rendered on-the-fly? Is it too
> > computationally intensive or would it have required too much rewrite of
> > the viewer?
>
> I thought they were rendered on-the-fly. Tables are rendered and drawn the first
> time they appear on the screen. (They are partially rendered by GetLineMetrics()
> to determine their size.)
Ahh. OK. I had assumed that they were being pre-rendered by the
distiller since I was seeing them in 1 BPP (I run at 16) and they were all
being displayed in little boxes to tap on instead of inline.
-alan
--
Alan Hoyle - [EMAIL PROTECTED] - http://www.alanhoyle.com/
"I don't want the world, I just want your half." -TMBG
Get Horizontal, Play Ultimate.
_______________________________________________
plucker-list mailing list
[EMAIL PROTECTED]
http://lists.rubberchicken.org/mailman/listinfo/plucker-list
