Thanks, Paulo - that's exactly what I needed - should have read a little more 
in the javadoc :)

Not to excuse my lack of reading the rest of the file, but it might be helpful 
to have a little more
explanation about this behaviour in the class level javadoc comment.
Also, there might be some reason behind the default behaviour that I don't 
understand, but I still
think that failing silently is generally a bad idea.

----- Original Message ----- 
From: "Paulo Soares" <[EMAIL PROTECTED]>
To: "Steve Appling" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Sent: Tuesday, November 16, 2004 5:38 PM
Subject: Re: [iText-questions] PdfPTable Cells bigger than a page


> (Someone that reads the javadocs, what a novelty.)
> That's old news. It's the default behavior but there's setSplitRows() and
> even setSpliLate() to choose when to split.
>
> Best Regards,
> Paulo Soares
>
> ----- Original Message ----- 
> From: "Steve Appling" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Tuesday, November 16, 2004 21:42
> Subject: [iText-questions] PdfPTable Cells bigger than a page
>
>
> > The PdfPTable class javadocs states "...if a row is bigger than the page
> it is dropped silently to
> > avoid infinite loops".
> > A few comments on this:
> >
> > Since PdfPTable doesn't support rowspans, I am using inner tables to
> accomplish the same layout.
> > Some inner tables may return results larger than will fit on one page.
> They are being dropped
> > silently as documented, but I'm not sure that is appropriate.  It seems
> more appropriate to throw an
> > exception if the contents can't be renedered.  I've been running tests on
> this application for a
> > while without noticing the data missing from the middle of the report.
> >
> > To make my application actually work, however, I would like to be able to
> handle inner tables that
> > are larger than a page.  Paulo, can you comment on what infinite loop is
> being avoided by dropping
> > these rows?  I am willing to work on adding support for this, but would
> appreciate any pointers on
> > where to start or problems that you anticipate with supporting this.  This
> is one area where
> > PdfTable seems to actually work better than PdfPTable, but I would much
> rather help improve
> > PdfPTable that fix all the other bugs in PDfTable.
> >
> >
> >
> >
> > -------------------------------------------------------
> > This SF.Net email is sponsored by: InterSystems CACHE
> > FREE OODBMS DOWNLOAD - A multidimensional database that combines
> > robust object and relational technologies, making it a perfect match
> > for Java, C++,COM, XML, ODBC and JDBC. www.intersystems.com/match8
> > _______________________________________________
> > iText-questions mailing list
> > [EMAIL PROTECTED]
> > https://lists.sourceforge.net/lists/listinfo/itext-questions
>




-------------------------------------------------------
This SF.Net email is sponsored by: InterSystems CACHE
FREE OODBMS DOWNLOAD - A multidimensional database that combines
robust object and relational technologies, making it a perfect match
for Java, C++,COM, XML, ODBC and JDBC. www.intersystems.com/match8
_______________________________________________
iText-questions mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/itext-questions

Reply via email to