Created attachment 130811 [details] PPTX file (PowerPoint 2007) with single "+" polygon, imported as two polygons with extra points Summary: * A single polygon gets imported as two polygons - one with fill/without line style and one without fill and with line style and without fill. * Each polygon contains two spurious point (unconnected to the actual polygon) Details: The attached file was created using MS PowerPoint 2007 and contains a slightly skewed drawing of a "+". In MS PowerPoint 2007: One has a single polygon with blue filling and a simple black solid line of width 1pt (with flat caps and round as join type). Clicking on edit points, the 4 outer and 4 inner points can be edited. In LO 4.3.0.3 and also in some older 4.2.x: Edit "Points" (F8) has no effect - one first needs to convert the shape "To Curve", "To Polygon, or "To Contour" (all have the same effect with regards to this bug. Namely, LO has then: * A group of two polygons, one "+" filled with blue and line style = none; another one consisting without fill but with line style: continuous, 0.04cm wide, round corner and flat caps. EXPECTED: A single polygon with the combined settings - not two polygons. * Editing either polygon, one has not only the expected 8 points (4 inner and 4 outer) but two additional points - one at the top-left corner of the bounding box and one at the bottom-left corner of the bounding box. Deleting them does not influence the shown shape - but they shouldn't be there at the first place.
Created attachment 130812 [details] comparison MSO 2010 and LibreOffice 5.4 I can't reproduce it in Version: 5.4.0.0.alpha0+ Build ID: fc53cce64400430cdc21f79c959d75fb9a26d13d CPU Threads: 4; OS Version: Linux 4.8; UI Render: default; VCL: gtk2; Locale: ca-ES (ca_ES.UTF-8); Calc: group
(In reply to Xisco Faulí from comment #1) > Created attachment 130812 [details] > comparison MSO 2010 and LibreOffice 5.4 > > I can't reproduce it in Version: 5.4.0.0.alpha0+ I am a bit confused by the screenshot: The issue is not that it is displayed in a different way, but issues with editing the imported graphic (due to the way it is imported). Thus, I am not sure whether you cannot reproduce it in 5.4 - or whether you simply have tried the wrong thing.
Could you please provide the clear steps to reproduce it then?
(In reply to Xisco Faulí from comment #3) > Could you please provide the clear steps to reproduce it then? Let me at least try to do so. * * * In LO: 1. Open the attached file 2. Right click on the graphic and choose in the menu: "Convert > To Curve" (or "Convert > To Polygon" or "Convert > To Contour") Expected: You get a single polygon. Actual result: You can do the following: 3. Right click on the graphic and choose: "Ungroup" 4. Click next to the graphic to deselect it 5. Click on it and drag. Expected: One drags the "+". Actual result: One drags the blue-filled polygon - revealing that the line around the "+" belongs to another polygon. [In PowerPoint: Open the file, right click on the graphic and choose "Edit points". That way, you edit that single polygon.] * * * The other issue seems to be unrelated to the PPTX import as it also happens when doing: (a) Click on the "<>" symbol in the toolbar and draw a "<>" (45 degree rotated rectangle) (b) Right click on the graphic and choose in the menu: "Convert > To Curve" (or "Convert > To Polygon" or "Convert > To Contour") (c) Press "F8" to edit the points. Expected: LO shows 4 points at the corners of the "<>" rectangle. Actual: LO shows 6 points, the 4 at the corner and one on the top-left of the bounding box and one on the bottom left of the bounding box. Those extra points seem to have no function - and can be dragged or deleted without any visual change.
(In reply to Tobias Burnus from comment #4) > Actual: LO shows 6 points, the 4 at the corner and one on the top-left of > the bounding box and one on the bottom left of the bounding box [...] The last one should be: bottom right (not left).
(In reply to Tobias Burnus from comment #4) > The other issue [i.e. spurious extra points] seems to be unrelated to the PPTX > import as it also happens when doing: That's known as bug 37559.
(In reply to Tobias Burnus from comment #4) > 1. Open the attached file > 2. Right click on the graphic > and choose in the menu: "Convert > To Curve" (or "Convert > To Polygon" > or "Convert > To Contour") > > Expected: You get a single polygon. > Actual result: You can do the following: > > 3. Right click on the graphic and choose: > "Ungroup" > 4. Click next to the graphic to deselect it > 5. Click on it and drag. > > Expected: One drags the "+". > Actual result: One drags the blue-filled polygon - revealing that the line > around the "+" belongs to another polygon. > > [In PowerPoint: Open the file, right click on the graphic and choose "Edit > points". That way, you edit that single polygon.] Reproduced. Arch Linux 64-bit, KDE Plasma 5 Version: 5.4.0.0.alpha0+ Build ID: ac8197327d3ef4f3c94fb0746393863404df086b CPU Threads: 8; OS Version: Linux 4.9; UI Render: default; VCL: kde4; Locale: fi-FI (fi_FI.UTF-8); Calc: group Built on February 11th 2016 Arch Linux 64-bit Version 3.6.7.2 (Build ID: e183d5b)
The two extra points seem to fixed with one of the recent commits. But I still get one polygon for the filling and a second polygon for the outline in Version: 6.1.0.0.alpha1+ (x64) Build ID: 88051c660fc6759346a01bc559818d3e23f8f55c CPU threads: 8; OS: Windows 10.0; UI render: default; Locale: de-DE (de_DE); Calc: CL
Created attachment 147032 [details] We have retested this problem and it seems to be fixed in version 6.1.2.
(In reply to NISZ LibreOffice Team from comment #9) > Created attachment 147032 [details] > We have retested this problem and it seems to be fixed in version 6.1.2. Wrong, not fixed, still repro like in comment 7 Arch Linux 64-bit Version: 6.3.0.0.alpha0+ Build ID: 51e6a95757906dff8b2819a4141bf3dc7938e95f CPU threads: 8; OS: Linux 4.19; UI render: default; VCL: gtk3_kde5; Locale: fi-FI (fi_FI.UTF-8); UI-Language: en-US Calc: threaded Built on 24 November 2018
Dear Tobias Burnus, 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
can't repro in Version: 6.5.0.0.alpha0+ (x64) Build ID: 32dcf3f0fdafcf44457842a8aa4f54d30d856ca9 CPU threads: 4; OS: Windows 10.0 Build 17763; UI render: GL; VCL: win; Locale: ru-RU (ru_RU); UI-Language: en-US Calc: threaded Buovjaga, please retest yourself
Still repro comment 7 Arch Linux 64-bit Version: 6.5.0.0.alpha0+ Build ID: 5f0db2c24c466e3c4cf0dc8faba1c62b38c770fd CPU threads: 8; OS: Linux 5.3; UI render: default; VCL: kf5; Locale: fi-FI (fi_FI.UTF-8); UI-Language: en-US Calc: threaded Built on 27 November 2019
Dear Tobias Burnus, 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