Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 332753 - Birt does a Pagebreak if pageRange is set.
Summary: Birt does a Pagebreak if pageRange is set.
Status: VERIFIED FIXED
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: BIRT (show other bugs)
Version: 2.6.1   Edit
Hardware: PC Windows 7
: P3 major (vote)
Target Milestone: 3.7.0 M7   Edit
Assignee: Yu Chen CLA
QA Contact: Xiaoying Gu CLA
URL:
Whiteboard: Obsolete
Keywords:
Depends on:
Blocks:
 
Reported: 2010-12-16 10:56 EST by pp CLA
Modified: 2011-04-05 23:50 EDT (History)
2 users (show)

See Also:

Attachments
An example of the bug (2.63 KB, application/pdf)
2010-12-16 11:00 EST, pp CLA 		no flags Details
The code that executes the report (3.11 KB, text/plain)
2010-12-16 11:05 EST, pp CLA 		no flags Details
The report that shows the bug (4.56 KB, application/octet-stream)
2010-12-16 11:07 EST, pp CLA 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description pp CLA 2010-12-16 10:56:57 EST 
Build Identifier: I20100608-0911

Configuration:
Birt 2.6.1
Seperate run and render task
Outputformat = PDF
PAGE_OVERFLOW = OUTPUT_TO_MULTIPLE_PAGES

If I render a 5 page report with a pageRange of for example "1,2-5",
A bug occures (I think it's to difficult to explain, so I attached an example).
However, if I don't set the pageRange, the report works fine.

Reproducible: Always

Steps to Reproduce:
1. Add two large Textelements (1 row more than there is space on a page)
2. Render the report with pageRange set to "1,2-n" (where n is the number of pages in total)
Comment 1 pp CLA 2010-12-16 11:00:49 EST 
Created attachment 185337 [details]
An example of the bug
Comment 2 pp CLA 2010-12-16 11:05:52 EST 
Created attachment 185341 [details]
The code that executes the report
Comment 3 pp CLA 2010-12-16 11:07:06 EST 
Created attachment 185342 [details]
The report that shows the bug
Comment 4 pp CLA 2010-12-16 11:14:29 EST 
I forgot to mention:
I've played with scripting and found out, that the onPageBreak-event of a surrounding element (table-detail for example) is not fired before the page with the two rows.
Comment 5 Xiaoying Gu CLA 2011-04-01 23:20:06 EDT 
The content in first page is displayed 2 pages because the label in the first page is split into 2 page.

User can avoid this problem by setting page range as "1-n".

Anyway, since the report is fixed-layout, we can output the first page as what it is.
Comment 6 Yu Chen CLA 2011-04-05 22:47:52 EDT 
Fixed.
Comment 7 Xiaoying Gu CLA 2011-04-05 23:50:02 EDT 
Verified in daily build 3.7.0.v201104050630