[reportlab-users] Table split

Robin Becker reportlab-users@reportlab.com
Tue, 15 Oct 2002 21:32:15 +0100

In article <20021015162850.7bdd9f4b.casey@zope.com>, Casey Duncan
<casey@zope.com> writes
>I don't disagree that the table is to blame, but it would be helpful if it 
>outputted some warning or even failed altogether if the table is too wide, 
>regardless of whether it is split.
>So, why not raise an assertion error here or is is possible for the layout 
>engine to recover from this in some cases? As it stands this seems much harder 
>to debug then it needs to be. There is no external indication that the table 
>width is the cause of this without some digging.
>It seems like it would be helpful for a warning log to be generated during 
>building to make tracking this down easier.
>P.S. Just so that I don't just sound like a complainer, I think this is an 
>excellent tool. It's obvious the amount of work and thought that has gone into 
>it. Thanks!
I have a feeling that we don't get an error message precisely because
someone in the past has disabled the width error checking in the frame
add method. I will have to think out how best to fix things up. 
Robin Becker