Description: UI: Line width in cm or in pt but not both Steps to Reproduce: 1. Open Writer 2. Insert -> Shape -> Line -> Line 3. Draw a line 4. A context toolbar appears on top -> Line width in cm 5. Sidebar -> Properties -> Line width pull down -> PT Actual Results: CM and PT are used Expected Results: PT or CM -> PT in my opinion.. as table borders are defined the same way Reproducible: Always User Profile Reset: No Additional Info: Version: 7.1.0.0.alpha0+ (x64) Build ID: 4c14c88cc681abab787a461a1bea502a777f37e6 CPU threads: 4; OS: Windows 6.3 Build 9600; UI render: Skia/Raster; VCL: win Locale: nl-NL (nl_NL); UI: en-US Calc: CL
(In reply to Telesto from comment #0) > Expected Results: > PT in my opinion Agreed. See also bug 72662 (comment 4) and bug 44267.
The toolbar follows the setting in Tools > Options > Writer > General, Sections Settings, field "Measurement unit". The sidebar should follow this setting too.
So in general setting measurement units of UI does need some attention. (In reply to Regina Henschel from comment #2) > The toolbar follows the setting in Tools > Options > Writer > General, > Sections Settings, field "Measurement unit". > The sidebar should follow this setting too. True, but discrete for each LO module. And the Sidebar content panels, toolbars and NB *should* follow that setting per module. But would make sense if the measurement units settings for UI could also be reset globally from *one* location? Perhaps on the Tools -> Options -> General pane? With option to override per module... As to unit choice, why Points? Equally valid to use Pixels, Twips, even mm--which would at least be at our 1/100mm native resolutions.
(In reply to V Stuart Foote from comment #3) > As to unit choice, why Points? Equally valid to use Pixels, Twips, even > mm--which would at least be at our 1/100mm native resolutions. Related to Points, that's based on Writer table border size + font size etc; not intended as general setting.
*** Bug 139225 has been marked as a duplicate of this bug. ***
*** Bug 105176 has been marked as a duplicate of this bug. ***
*** Bug 121635 has been marked as a duplicate of this bug. ***
Dear Telesto, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug