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
This is quite hard to explain with words.
Say you have created a new 2-column table item.
If you try to drag the column widths with the mouse to make e.g. the first column ca. 3 cm wide, this results in the first column having a width of (available-width - 3 cm).
This did not happen in BIRT 4.2.1.
OTOH, in BIRT 4.2.1, dragging the column width of any column caused every column to have a fixed width - and the table as a whole, too.
Now, in the 2-column example, the second column has no specified width - which is good.
When coaching, I always tell users to not use the mouse to set column widths, because I think it's usually much better if the table and at least one column do not have a specified width. With newer BIRT releases, this recommendation is no longer as important as before.
I guess this issue and the changed behavior in comparison to 4.2.1 are closely related.
I'll try to fix this myself after I'll have created PRs for some other bugs.
The text was updated successfully, but these errors were encountered:
This is quite hard to explain with words.
Say you have created a new 2-column table item.
If you try to drag the column widths with the mouse to make e.g. the first column ca. 3 cm wide, this results in the first column having a width of (available-width - 3 cm).
This did not happen in BIRT 4.2.1.
OTOH, in BIRT 4.2.1, dragging the column width of any column caused every column to have a fixed width - and the table as a whole, too.
Now, in the 2-column example, the second column has no specified width - which is good.
When coaching, I always tell users to not use the mouse to set column widths, because I think it's usually much better if the table and at least one column do not have a specified width. With newer BIRT releases, this recommendation is no longer as important as before.
I guess this issue and the changed behavior in comparison to 4.2.1 are closely related.
I'll try to fix this myself after I'll have created PRs for some other bugs.
The text was updated successfully, but these errors were encountered: