Bug 122058 - REPORTBUILDER: Measurement unit couldn't be chosen, but point is used internal
Summary: REPORTBUILDER: Measurement unit couldn't be chosen, but point is used internal
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Base (show other bugs)
Version:
(earliest affected)
5.1.5.2 release
Hardware: All All
: medium enhancement
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: Database-Reports-Builder
  Show dependency treegraph
 
Reported: 2018-12-12 18:46 UTC by Robert Großkopf
Modified: 2019-01-15 09:36 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments
Open the two reports and switch to "Edit document" - see the empty columns in first report (61.84 KB, application/vnd.oasis.opendocument.database)
2018-12-12 18:46 UTC, Robert Großkopf
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Robert Großkopf 2018-12-12 18:46:51 UTC
Created attachment 147478 [details]
Open the two reports and switch to "Edit document" - see the empty columns in first report

Positioning of elements in reports is a little bit tricky. You couldn't place one element over another. If you see the values in the properties of a field sometimes a field couldn't be set directly beneath another, because Report-Builder internal rounds the values to measurement unit "Point".

In Writer you could switch to point, but when editing a report you could only set local settings to, for example, English (USA) to get inch. So you could switch to 0.25 inch (18 points) and all multiplications to position the fields exactly.

You could have a look to the attached example. The first report is positioned with unit 'cm', the second with unit 'inch' - but exactly set to multiples of 0.25 inch = 18 points. Execute the reports and press "Edit document". Have a look at the tables. There are small empty columns, which have a with of 0.04 cm in the first report. In the second report the tables all look fine - only 4 columns for the content of four columns.

We should add the possibility to set the measurement unit to "Point" for better positioning. Could be the reports will run better and faster then - but this I haven't tested.
Comment 1 Alex Thurgood 2019-01-14 11:34:35 UTC
Confirming with 

Version: 6.2.0.2
Build ID: 2ce5217b30a543f7666022df50f0562f82be0cff
CPU threads: 4; OS: Mac OS X 10.14.2; UI render: default; VCL: osx; 
Locale: fr-FR (fr_FR.UTF-8); UI-Language: en-US
Calc: threaded

Robert : has this problem always been in LO, or is it a regression ?
Comment 2 Robert Großkopf 2019-01-14 15:07:24 UTC
(In reply to Alex Thurgood from comment #1)
> 
> Robert : has this problem always been in LO, or is it a regression ?

Couldn't test it with the first version, but it's the same in LO 5.1.5.2. Think there has never been a possibility to change the measurement in the Report-Builder. So no regression.