Created attachment 190382 [details] Document exhibiting the bug Consider the attached presentation. It was produced as follows: 1. New presentation 2. Delete default elements 3. Insert a rectangle 4. Set fill to None 5. Set Line Width to 6 pt 6. Set Line style/type to Dashed 7. Play with rectangle dimensions a bit You'll notice that the corners have jagged artifacts. While one can understand why these were produced (rendering each edge irrespective of the intersecting edge) - it is unaesthetic, jarring, and is not how a person would trace a dashed path. I suggest that when we have "small parts of dashing", which do not exceed the intersection with the other edge; and another edge with a dash intersecting the edge of the intersection - the "small part of a dash" not be rendered at all. Alternatively, the placement of spaces between dashes can be follow the circumference, so that dashes of consecutive edges can (more-or-less) never intersect. See with: Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 3161a6c351a2f5f70c0420ee8cccf2eb23de1ecf CPU threads: 4; OS: Linux 6.5; UI render: default; VCL: gtk3 Locale: he-IL (en_IL); UI: en-US
Created attachment 190383 [details] Screenshot of LO Impress window with attachment 190382 [details]
Confirm with Version: 7.6.0.3 (X86_64) / LibreOffice Community Build ID: 69edd8b8ebc41d00b4de3915dc82f8f0fc3b6265 CPU threads: 4; OS: Windows 10.0 Build 19045; UI render: default; VCL: win Locale: ro-RO (en_US); UI: en-US Calc: threaded
Dear Eyal Rozenberg, 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
Bug still manifests with: Version: 26.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 062b4fd5635c906d7b8c3a68189faecb9dc6dabd CPU threads: 4; OS: Linux 6.12; UI render: default; VCL: gtk3 Locale: en-IL (en_IL); UI: en-US