Created attachment 110429 [details] Input file for issues A & B This bug report includes 3 related issues or aspects of the same issue. Testing was done with LO 4.2.0.4 and 4.3.4.1 on Ubuntu, as described below. 1. Start with "dwg 1 ver. 1- from Inkscape.pdf" (the ultimate source of the diagram was FreeCAD; then Inkscape was used to make a few edits & convert SVG to PDF). 2. Open this file in LO Draw 4.2.0.4. 3. This 2D diagram has a hollow region at the top & one at the bottom. The user wants to fill these 2 regions with a hatch pattern. 4. First, the top region. Select the 13 draw objects that form the boundary of this region. These are 12 lines (including, at the right-hand side, a very short vertical line which is difficult to select) & one bezier. 5. Modify > Connect 6. In the "Line and Filling" toolbar, set Area Style/Filling to "Hatching - Black 45 degrees". 7. LO Draw 4.2.0.4 does this correctly. 8. Issue A: In step 5, LO Draw 4.3.4.1 produces 1 or 2 short extra line segments, forming an acute angle, sticking out at the right-hand side. 9. Next, the bottom region. Follow steps 4 & 5 for this region. 10. Issue B: In both versions of LO Draw, an extra oblique line appears at the lower left. The results of the above 2 issues in the 2 versions of Draw are shown in the two "dwg 1 ver. 2.odg" files. About Issue B: * Using "edit points" mode (the Points button in the Drawing toolbar) to move the right-hand endpoint of the unexpected line (e.g., slightly up & to the left) and the lower-left corner of the region (e.g., slightly down & to the left) shows that a total of 3 extra lines were drawn, 2 of which coincided with lines that were present in the PDF. * Trying to "nudge" the segments (using "Snap to Object Points" in the Options toolbar, before the Connect command), so their endpoints exactly coincided, typically didn't prevent the extra lines from being drawn. In my testing, it did once out of several tries. But even if there is always a procedure of "nudging" the lines that will hide Issue B, I think it is unreasonable to expect the user to do this. The set of lines looks closed to the user, even at high zoom factors, so LO Draw should be able to connect them with only the Modify > Connect command. 11. "dwg 2 ver. 1- from Inkscape.pdf" is similar, up through step 8 of the above. (This time there are 12 draw objects forming the boundary of each region of interest.) 12. Issue C: For the bottom region, at step 6, in both versions of LO Draw, the hatch pattern isn't drawn, because the bezier isn't closed. The user needs to click "Close Bézier" on the Edit Points toolbar. 13. Once that button is clicked, Issue B (extra line obliquely across the region) occurs in both versions of LO Draw, and Issue A (acute angle sticking out at a junction point) occurs (again) in 4.3.4.1. ----- There is a workaround for Issue B, taking advantage of the fact that the bottom region is a mirror image of the top region, and that the top region is correctly connected into a bezier by LO Draw (at least version 4.2.0.4). I will summarize as: * Edit > Duplicate * Modify > Flip > Vertically * Modify > Break * Snap to Object Points * Modify > Connect As with "nudging," I think the user shouldn't have to do this workaround. Thanks for help with these issues.
Created attachment 110430 [details] Output file from 4.2.0.4, issue B
Created attachment 110431 [details] Output file from 4.3.4.1, issues A & B
Created attachment 110432 [details] Input file for issues A, B, C
Created attachment 110433 [details] Output file from 4.2.0.4, issues B & C
Created attachment 110434 [details] Output file from 4.3.4.1, issues A, B, C
The filenames mentioned in the bug description are viewable by clicking the Details links in Bugzilla.
** Please read this message in its entirety before responding ** 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 on a currently supported version of LibreOffice (5.0.4 or later) https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System 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) http://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: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for your help! -- The LibreOffice QA Team This NEW Message was generated on: 2015-12-20
** Please read this message in its entirety before responding ** 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 on a currently supported version of LibreOffice (5.1.6 or 5.2.3 https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System 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) http://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: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug-20170103
Dear dg1727, 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 http://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! Warm Regards, QA Team MassPing-UntouchedBug
Dear dg1727, 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
dg1727, a bug will stay in Unconfirmed status until someone else can confirm it, and will mark the bug as New. Please wait for someone to test this bug. Thank you for reporting this.
The command is now Shape - Connect. I selected the parts by painting a selection rectangle. It selected 14 parts, though. I reproduce the issues A and B. Issue C is no longer possible to reach as LibreOffice doesn't allow access to Area. Issue A happens after 9616b786adb9491f7c26fc0f1053e7b3d1b35f27 fdo#45003 PDF import: Implementing linejoin and linecap properties Not sure, if this can be called a regression as such. I created bug 156190 for issue B, because we should have one report per issue. Arch Linux 64-bit, X11 Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 445ab2355333ddb46081baffb8b0e3bb14fe00b3 CPU threads: 8; OS: Linux 6.4; UI render: default; VCL: kf5 (cairo+xcb) Locale: fi-FI (fi_FI.UTF-8); UI: en-US Calc: threaded Built on 7 July 2023