[reportlab-users] RE: splitting in table cells

[Henning von Bargen]

To answer my own question:
It doesn't work with 1.20, either.

So I've started writing my own patch.
The current status is:
* It is working in principle, at least
  if the cells do contain paragraphs.
* It should be possible to extend the 
  solution for strings and other flowables, too.
* However, handling sequences (lists, tuples)
  of other objects would be more complicated.

And I'm still facing one specific problem regarding the 
styles/lines/backgrounds: Since I'm splitting a row in the 
table, in effect I have to duplicate a row in the middle 
of the table and I don't know how to adopt the internal 
routines cr_0_0 etc.

I'd like to send my code to the main developer of tables.py
for a review - perhaps someone at ReportLab could continue
my efforts?

Henning

> -----Ursprüngliche Nachricht-----
> 
> Message: 1
> Date: Mon, 3 Jan 2005 12:14:50 +0100 
> From: Henning von Bargen <H.vonBargen at triestram-partner.de>
> Subject: [reportlab-users] splitting in table cells?
> To: "'reportlab-users at reportlab.com'" <reportlab-users at reportlab.com>
> Message-ID: <71674BEFF0E2D41196F500600811AA6B5BB18F at TUP-BO1-EXC>
> Content-Type: text/plain;	charset="iso-8859-1"
> 
> Hi,
> 
> is it possible to allow splitting INSIDE a table row
> if the single row is too high to fit on a single page
> (or: if the calculated row height is > X)?
> 
> To be more precise:
> If the table has header rows, take these into account.
> If the header rows themselves don't fit, raising an exception is ok,
> if header rows + first data row don't fit: split inside this data row.
> 
> One of my customers is printing tables in a productive environment
> (using RL 1.19) where this is actually a problem.
> 
> for a simple example, think of a 2x2 table,
> each column 5cm wide, each cell containing a paragraph 
> ("this is all nonsense." * 2000)
> 
> This will cause an exception in 1.19
> 
> Henning
>