Pranit wrote: > The problem I am facing is that when there are huge tables and I use row > spans, the row spans span onto a few pages making the report difficult to > understand as there an entire column without data sometimes even two.
Isn't that a consequence that was to be expected when using rowspan? Depending on the context, you could: - use a table header (that way the column isn't entirely empty) - switch to using nested tables (I don't know if this solves anything, but it could give you more control). - use table/cell events (again: without seeing the project and the data that goes into the table, I can guarantee this solves anything.) - ... > Can anybody suggest me how to repeat the row data only once on each page if > there is a span and the page has to go to the next page? At first sight, I'd say: don't add the content that needs to be repeated to the cell, but add it to a cell event. > Also I have noticed that the performance takes a big hit when I have tables > who implement a lot of row spans, is there any particular explanation for > that? If you use rowspan, iText has to "think several rows ahead". While constructing the rows, it has to "look back several rows". That's expensive in terms of CPU. -- This answer is provided by 1T3XT BVBA http://www.1t3xt.com/ - http://www.1t3xt.info ------------------------------------------------------------------------------ Return on Information: Google Enterprise Search pays you back Get the facts. http://p.sf.net/sfu/google-dev2dev _______________________________________________ iText-questions mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/itext-questions Buy the iText book: http://www.1t3xt.com/docs/book.php Check the site with examples before you ask questions: http://www.1t3xt.info/examples/ You can also search the keywords list: http://1t3xt.info/tutorials/keywords/
