Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 313294

Summary: [Improve Page Break Management] Repeat a column after a page break
Product: z_Archived Reporter: Jeff <jfrancois.arnaud>
Component: BIRTAssignee: Birt-ReportEngine-inbox <Birt-ReportEngine-inbox>
Status: CLOSED DUPLICATE QA Contact:
Severity: major    
Priority: P3 CC: hustlg, jfrancois.arnaud
Version: 2.5.1   
Target Milestone: ---   
Hardware: PC   
OS: Windows XP   
Whiteboard:
Attachments:
Description Flags
It contains 2 pdf generated with birt : 1 pdf of what happend and 1 pdf of the behavior I expected none

Description Jeff CLA 2010-05-18 04:20:06 EDT
Created attachment 168870 [details]
It contains 2 pdf generated with birt : 1 pdf of what happend and 1 pdf of the behavior I expected

I have a simple report that contains only a table.
My table has 7 big columns, so the width of my table is bigger than the page's width.

When I export my report to a .pdf file, it looks like this:

Page 1 :
+-----------+-----------+-----------+-----------+-----------+
| Column 1  | Column 2  | Column 3  | Column 4  | Column 5  |
+-----------+-----------+-----------+-----------+-----------+

Page 2 :
+-----------+-----------+-----------+-----------+-----------+
| Column 1  | Column 2  | Column 3  | Column 4  | Column 5  |
+-----------+-----------+-----------+-----------+-----------+
Page 3 :
Code :
+--------------+-----------+
| Column 6     | Column 7  |
+--------------+-----------+

Page 4 :
Code :
+--------------+-----------+
| Column 6     | Column 7  |
+--------------+-----------+

And the problem is that if I read the page 3 or 4, I will not be able to know which row is concerned, which row of the page 1 is continued on the page 3... that's why I would like to write again on page 3 and 4, the contain of the Column 1 (a simple "line #" for example).
It might be a "repeatAfterPageBreak"property on each column, in order to do this.
Comment 1 Gang Liu CLA 2010-05-25 06:22:43 EDT

*** This bug has been marked as a duplicate of bug 263204 ***