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

Bug 207568

Summary:

BIRT standalone Designer Fixed Colum width presentation

Product:

z_Archived

Reporter:

Virgil Green <vjg>

Component:

BIRT

Assignee:

Dazheng Gao <gump_gao>

Status:

VERIFIED FIXED

QA Contact:

Xiaodan Wang <xwang>

Severity:

normal

Priority:

CC:

slee, vjg, wenfeng.fwd, xwang, zqian

Version:

2.2.1

Keywords:

plan

Target Milestone:

2.5.0 M7

Hardware:

OS:

Windows XP

Whiteboard:

Non-Auto

Attachments:

Description	Flags
Sample Report Design	none

Description Virgil Green

2007-10-26 08:02:18 EDT

Build ID: v20070924-0630

Steps To Reproduce:
1. Create new report
2. Create table with fixed-width columns, each column being .5 inches and enough columns to use entire width between margins.
3. Bind to table fields with field names that cause designer's column width to exceed width shown when unbound.

More information:
I just downloaded and installed the 2.2.1 standalone designer. I copied a 
.rptdesign file from my 2.1.2 workspace to the 2.2.1 workspace and then opened 
it.

Unlike in 2.1.2, the layout mode in 2.2.1 doesn't give an accurate (or even 
close) representation of the report format. The second table in my report 
has 10 data cells/fields. They are set to 3 in wide for the first cell and 
.5 inches for each of the remaining cells, totaling 7.5 inches.

In 2.1.2, the layout view showed all the fields within the defined margins. 
When the data cells showed the bound field names, the cells would expand 
vertically and the field name would wrap. In 2.2.1, the cell's width expands 
to include the field name without wrapping, the cells have variable visible 
widths, and the table extends outside the margins of the report.

The report in preview mode works fine. This layout problam only exists in 
the layout view.

Is there new setting to affect this behavior or is this a bug?

This also occurred in 2.2.

Comment 1 Virgil Green

2007-10-26 08:05:55 EDT

Created attachment 81255 [details]
Sample Report Design

Comment 2 Zhiqiang Qian

2007-10-29 04:04:42 EDT

This is an intended change to support auto-layout in report designer since 2.2.0.

Comment 3 Virgil Green

2007-10-29 23:45:49 EDT

While I can appreciate the need to have an autolayout feature, there is also a need for fixed format design of forms. With the designer in its current state, fixed format forms are almost impossible to visualize when they have fields bound to them. I have to manually track all of the design work so I know what has and hasn't been completed since the visual representation is so misleading.

Comment 4 Virgil Green

2007-10-29 23:48:51 EDT

(In reply to comment #2)
> This is an intended change to support auto-layout in report designer since
> 2.2.0.

I suggest truncating the bound field name and using fly-over hint text to show the full name. This might be controlled by a preference setting in case someone prefers the current presentation. The previous version expanded vertically and wrapped the field name within the defined column width. That wasn't ideal, but it was certainly preferable to expanding horizontally.

Comment 5 Zhiqiang Qian

2007-10-30 22:59:34 EDT

(In reply to comment #4)
> I suggest truncating the bound field name and using fly-over hint text to show
> the full name. This might be controlled by a preference setting in case someone
> prefers the current presentation. The previous version expanded vertically and
> wrapped the field name within the defined column width. That wasn't ideal, but
> it was certainly preferable to expanding horizontally.
> 
Yes, this is actually the desired behavior of "fixed layout", which is not implemented yet. You can see a "layout preference" setting there for Report Design already in Properties view.

Comment 6 Zhiqiang Qian

2008-08-18 06:13:02 EDT

*** Bug 244399 has been marked as a duplicate of this bug. ***

Comment 7 Zhiqiang Qian

2008-08-18 06:13:27 EDT

*** Bug 244400 has been marked as a duplicate of this bug. ***

Comment 8 Dazheng Gao

2009-04-01 02:59:01 EDT

Fixed.

Comment 9 Xiaodan Wang

2009-04-13 02:19:01 EDT

Open new entry for the issues still exists.

Verified in build (2.5.0.v20090413-0630).