You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In PdfPTable, we have support to write tables in two ways:
document.add(table);
table.writeSelectedRows();
In the first approach, if a table row's content is too long to fit on a single page, the content is properly split across multiple pages. However, the same handling is not available in the second approach leading to data loss.
Can someone guide me on how to achieve the similar behavior in the second approach?
Or, please navigate me to the respective code logic that handles this behavior in the first approach.
PDF via document.add(table);
PDF via table.writeSelectedRows();
Thank you!
The text was updated successfully, but these errors were encountered:
Thank you for your response. However, using Table does not meet my requirements. My use case involves multi-lingual text, images, icons, symbols, and shapes within a table cell. Therefore, I am utilizing PdfPTable.
I am handling large datasets, including hundreds of thousands of rows, which makes it impractical to hold all chunks, phrases, PdfPCells, and rows in the JVM. To manage this, I am using PdfPTable.writeSelectedRows() to write the table row by row.
Additionally, I need to position my table at a specific positionX and start from a particular positionY within a specified width.
Hello,
In PdfPTable, we have support to write tables in two ways:
In the first approach, if a table row's content is too long to fit on a single page, the content is properly split across multiple pages. However, the same handling is not available in the second approach leading to data loss.
Can someone guide me on how to achieve the similar behavior in the second approach?
Or, please navigate me to the respective code logic that handles this behavior in the first approach.
PDF via document.add(table);
PDF via table.writeSelectedRows();
Thank you!
The text was updated successfully, but these errors were encountered: