Description: [MS-EMF] describes two values for PolygonFillMode enum: Alternate = 1 Winding = 2 LO seems to ignore 'winding' mode and apply 'alternate'. Steps to Reproduce: Open EMF sample (star_pfm2.emf) in LO. Actual Results: Both stars rendered with unfilled pentagon in the center Expected Results: Bottom star should be fully filled. Reproducible: Always User Profile Reset: No Additional Info: Implementation in MSO for Windows seems to consider anything other than 1 as "Winding". Implementation in MS wordpad seems to consider anything other than 2 as "Alternate". Because of the inconsistency in MS own implementation, decision is needed with what to be compatible.
Created attachment 171570 [details] EMF sample PolyfillMode is set to 1 before top star record. It set to 2 after that before the bottom start record.
Created attachment 171571 [details] Screenshot of the sample file in MSO for win
Created attachment 171572 [details] EMF with PolyfillMode set to 0 beforr the bottom star record (for completeness, a file with undocumented value in SetPolyfillMode Mode)
Created attachment 171573 [details] EMF with PolyfillMode set to 6 before the bottom star record
Code pointer I suppose: https://opengrok.libreoffice.org/xref/core/emfio/source/reader/emfreader.cxx?r=b5602d5c#1034
confirm in Version: 7.2.0.0.alpha0+ / LibreOffice Community Build ID: a52590d76b89dc75be2aa87f4287624c89f1e82f CPU threads: 4; OS: Mac OS X 11.3; UI render: default; VCL: osx Locale: ru-RU (ru_RU.UTF-8); UI: en-US Calc: threaded
Hossein, is this related to the work you are doing on winding?
(In reply to Chris Sherlock from comment #7) > Hossein, is this related to the work you are doing on winding? Chris: Yes. Please take a look at: tdf#84199. It depends on this issue.
Dear Valek Filippov, 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