Created attachment 174906 [details] Example file with four non-primitive custom-shapes Open attached file. It contains four shapes and next to it the markup of the enhanced-path attribute. A is correct. The path is closed by command Z and therefore has no markers. B is wrong. The path is not closed but has only accidentally same coordinates in start and end point. It should show markers. This is a custom shape with an enhanced-path. The handling of polyline and polygon does not apply. C is wrong. The path is closed by command Z and therefore should show no markers. Difference to A is, that here exists a second sub-paths set (starting after the N command) that has a line. D is wrong. The path is not closed and therefore should show markers. It is the same as B but with an addition second sub-paths set with a line.
Created attachment 174907 [details] Example file with five non-primitive custom-shapes Correction: C is OK E is wrong, because a closed path should not have markers regardless of other sub-paths in the same set.
Moving to NEW
Dear Regina Henschel, 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
The rendering of markers is still wrong in Version: 26.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 7f4868348c14b305fcd75744e1e3544d0d3a5d61 CPU threads: 32; OS: Windows 11 X86_64 (build 26100); UI render: Skia/Vulkan; VCL: win Locale: de-DE (de_DE); UI: en-US Calc: threaded