When using e.g. the 'smiley' CustomShape and extruding it MS-Style, the 3D representation works, but the 'eyes' and 'mouth' are pretty much invisible. They are there but not really visible.
Compared with competitor, the eyes and mouth is clearly vsisible, on both sides of the 3D-Shape (check by rotating).
This is a follow-up to tdf#118498, just a visual annoyance and should be fixed by changing the internal creation of the visual representation of CustomShapes. Currently, 'hidden' SdrObjects are created and visualized. This may be used, but for 3D, overlaying shapes would need to be depth-arranged to guarantee a visualizazion.
Even better would be to get rid of these 'hidden' SdrObjects and create primitive visualisation data immediately - but that would need bigger changes.
Created attachment 143593 [details]
PowerPoint example for comparison
PowerPoint has a different concept. It makes the extrusion from the outer outline and has contour line (violet in example) and extrusion depth and color (red in example) for this 3D-object. Then it draws the original shape like a texture on the front and on the back face with the area fill color (yellow in example) and the line color (green in example) of the original shape. PowerPoint does not take the sub-paths as separate 3D-objects. The sub-paths are missing in Wireframe mode in PowerPoint.
This is only a description for PowerPoint. I do not find in the spec how an extrusion of sub-paths has to be done in case of the enhanced-geometry of a custom-shape.
The file has objects and picture of the objects.
Dear Armin Le Grand (CIB),
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://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa
Thank you for helping us make LibreOffice even better for everyone!
The problem exists still as described in Version: 18.104.22.168.alpha0+ (x64) / LibreOffice Community
Build ID: 604d464d2bdd0271ad63e5c93d4869a318eac262
CPU threads: 8; OS: Windows 10.0 Build 19043; UI render: Skia/Raster; VCL: win
Locale: de-DE (en_US); UI: en-US