Border line size of shape is defined in cm in the line dialog (default is 0,05 pt, which shows as 0,00 cm)
Steps to Reproduce:
1. Open Draw
2. Insert a rectangle
3. Format -> Line
4. Notice a line size of 0,00 cm (with united of measurement set to cm (default)
Point seems to be a more logical united use (same as in the sidebar or for table borders in Writer)
User Profile Reset: No
Build ID: d71ea82055a6a304493c7eaa90809a348e23784d
CPU threads: 4; OS: Windows 6.3; UI render: GL; VCL: win;
TinderBox: Win-x86@42, Branch:master, Time: 2018-11-19_03:25:07
Locale: nl-NL (nl_NL); UI-Language: en-US
Can not confirm with
Build ID: 0c292870b25a325b5ed35f6b45599d2ea4458e77
CPU threads: 2; OS: Windows 6.1; UI render: default;
Locale: en-US (en_US); Calc: group
(In reply to Durgapriyanka from comment #1)
> Can not confirm with
> Version: 22.214.171.124
> Build ID: 0c292870b25a325b5ed35f6b45599d2ea4458e77
> CPU threads: 2; OS: Windows 6.1; UI render: default;
> Locale: en-US (en_US); Calc: group
It's slightly depending on locale of course. USA will be inches. It's possible to change the Unit of Measurement of course.
(In reply to Telesto from comment #2)
> (In reply to Durgapriyanka from comment #1)
> > Can not confirm with
> > Version: 126.96.36.199
> > Build ID: 0c292870b25a325b5ed35f6b45599d2ea4458e77
> > CPU threads: 2; OS: Windows 6.1; UI render: default;
> > Locale: en-US (en_US); Calc: group
> It's slightly depending on locale of course. USA will be inches. It's
> possible to change the Unit of Measurement of course.
Yes, I do have it in inches. I agree with your comment.
Created attachment 147124 [details]
bug reproduced by Version: 188.8.131.52.alpha0+
i follow the step to reproduce and found the bug still exist.
attached is the screenshot of my result
Version: 184.108.40.206.alpha0+ (x64)
Build ID: 0f25a3c36f27fd51453b9a9115f236b83c143684
CPU threads: 8; OS: Windows 10.0; UI render: GL; VCL: win;
TinderBox: Win-x86_64@42, Branch:master, Time: 2018-11-27_20:06:55
Locale: zh-TW (zh_TW); UI-Language: en-US
Yep, already in 3.3.0.
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://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa
Thank you for helping us make LibreOffice even better for everyone!
Added as duplicate of #134448 which as more details
*** This bug has been marked as a duplicate of bug 134448 ***