Bruno, the requirement is that at each onTableEvent you need to know in
advance if the table is split or not so that you can take actions like
dashed border at the bottom if table is split or ctnd on next page text at
the lower right corner of the table and just a simple border if table fits
in the current page. By using onTableEvent only you can collect information
on the first pass and possibly do a second pass to do layout based on
collected info. Alternatively, you can try to decide if table fits on the
current page onTableLayout method using the cell row and height information
but that proved not to be a sound way for me with cell paddings and some
offsets involved in values.
Riffla, if you try to update cells via normal means (I mean adding cell or
so) it will not take any effect as the table has already been rendered at
the time you receive the callback.
On Thu, Oct 14, 2010 at 2:42 AM, riffla <[email protected]> wrote:
>
> Hi again
>
> Thanks alot for your advices...
> But I'm still struggling a bit with how to use let's say the PdfPTableEvent
> (or rather the implementation of the interface).
>
> As it is designed right now I use PdfContentByte to add things
> (showTextAligned). Will that affect the way I need to implement my needs...
>
> Assume I implement PdfPTableEvent and in the tableLayout method I get a
> reference to the rendered table (or, in case of a page break, the part of
> the table just rendered), will I be able to change the text within the
> header row here. Lets say at the start of the table had the following
> header
> row (with colspan covering entire row) "Employees", and on all subsequent
> pages that starts with a split part of the table I want the header row to
> read "Employees (continued from previous page)". Will that be possible?
> /R
> --
> View this message in context:
> http://itext-general.2136553.n4.nabble.com/Choice-of-method-tp2993417p2994875.html
> Sent from the iText - General mailing list archive at Nabble.com.
>
>
> ------------------------------------------------------------------------------
> Beautiful is writing same markup. Internet Explorer 9 supports
> standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 & L3.
> Spend less time writing and rewriting code and more time creating great
> experiences on the web. Be a part of the beta today.
> http://p.sf.net/sfu/beautyoftheweb
> _______________________________________________
> iText-questions mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/itext-questions
>
> Many questions posted to this list can (and will) be answered with a
> reference to the iText book: http://www.itextpdf.com/book/
> Please check the keywords list before you ask for examples:
> http://itextpdf.com/themes/keywords.php
>
--
Nurettin DAG
------------------------------------------------------------------------------
Beautiful is writing same markup. Internet Explorer 9 supports
standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 & L3.
Spend less time writing and rewriting code and more time creating great
experiences on the web. Be a part of the beta today.
http://p.sf.net/sfu/beautyoftheweb
_______________________________________________
iText-questions mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/itext-questions
Many questions posted to this list can (and will) be answered with a reference
to the iText book: http://www.itextpdf.com/book/
Please check the keywords list before you ask for examples:
http://itextpdf.com/themes/keywords.php
