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

Bug 335058

Summary:	Add default Page Break Interval to Report Design Preferences
Product:	z_Archived	Reporter:	Kevin Rahe <KevinR>
Component:	BIRT	Assignee:	Birt-ReportDesigner <Birt-ReportDesigner-inbox>
Status:	REOPENED ---	QA Contact:	Xiaoying Gu <bluesoldier>
Severity:	enhancement
Priority:	P3	CC:	bluesoldier, jianchao.li
Version:	2.6.1
Target Milestone:	---
Hardware:	PC
OS:	Windows 7
Whiteboard:	Obsolete

Description Kevin Rahe

2011-01-21 16:04:46 EST

Build Identifier: M20100909-0800

Whenever a Table is added to a report, either by dragging a Data Set or a Table element from the Palette to the Layout, the default value for Page Break Interval is set to 40.  Not only is such an arbitrary value never likely to be correct for a given report, but it's very easy to forget to change it to the desired value which is almost always 0.  I've often gotten all the way to deploying a report without noticing the problem, then realizing I forgot something when a user complains about a pagination problem.

Reproducible: Always

Steps to Reproduce:
1.  Create a new report.
2.  Drag a Data Set or Table from the Palette to the Layout.
3.  Select the newly-added table, then the Page Break tab in the Property Editor.

Comment 1 Xiaoying Gu

2011-02-23 20:29:07 EST

The default page break interval is determined according to our experiences. It always generate 40 data rows into one page in PDF format if using the default settings.
The pagination is useful and somehow required since we can't generate too much content into one page in html, pdf and so on.
So that this requirement that change the default page break interval into 0 is invalid.

Comment 2 Kevin Rahe

2011-02-23 21:42:02 EST

Perhaps it would be more appropriate for the Default Page Break Interval to be configurable in the Report Design Preferences, rather than hard-coded.  I'm not sure what category would be most appropriate - perhaps Layout.  I have reopened this as an enhancement request.