[reportlab-users] Table split

Casey Duncan reportlab-users@reportlab.com
Tue, 15 Oct 2002 15:34:50 -0400

On Tue, 15 Oct 2002 20:11:51 +0100
Robin Becker <robin@reportlab.com> wrote:

> In article <20021015150135.7cdc2d8c.casey@zope.com>, Casey Duncan
> <casey@zope.com> writes
> >Why does the width of the table come into play during the row split?
> >
> >-Casey
> I think the idea is that if it can't fit across then splitting won't
> help so we fail early. A long wide table won't fit and two short wide
> ones won't either.
> -- 
> Robin Becker

But this is a vertical split across a page break. The table physically fits on the page horizontally, although it is a half-a-dozen or so points too wide according to availWidth anyhow. I guess I'm not taking into account padding or something. Reportlab didn't complain though and it was not visually evident, even with borders.

I guess its just weird to have the table draw ok as long as it fits on one page (even if it is too wide) and fail mysteriously when it tries to split across pages. The error message (and some inline comments) makes it seem like there were empty paragraph flowables to blame, which was what I started out looking for.

Is split called when the table is too wide as well? Why not just raise an error here instead of returning an empty list?