Bug 131783 - 3D object fill projection mode "Circular" has gap for bitmap fill
Summary: 3D object fill projection mode "Circular" has gap for bitmap fill
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Draw (show other bugs)
Version:
(earliest affected)
Inherited From OOo
Hardware: x86-64 (AMD64) Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: Object-Fill-Bitmap
  Show dependency treegraph
 
Reported: 2020-04-01 13:05 UTC by Regina Henschel
Modified: 2022-09-29 03:54 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments
Examples of 3D objects with bitmap fill and projection "Circular" (130.70 KB, application/vnd.oasis.opendocument.graphics)
2020-04-01 13:05 UTC, Regina Henschel
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Regina Henschel 2020-04-01 13:05:51 UTC
Created attachment 159224 [details]
Examples of 3D objects with bitmap fill and projection "Circular"

Open attached document. It has some examples of the problem.

Use a cube or an extrusion object generated from rectangle for example.
Set the Area fill style to "Bitmap",  select a bitmap.
Set style "Stretched" or set style "Custom position/size" with alignment "Center left".
Set the projection mode to "Circular". That is in the "3D effects" dialog on tab "Textures".
Turn the object so that you can see the left side and possibly part of the back side.

The bitmap starts in the middle of the left side and goes around the body. That is OK for "Circular".

Error: At the end the bitmap is not brought to the middle of the left side, but it is cut at the back side.
Comment 1 Buovjaga 2020-06-20 11:51:54 UTC
Confirmed

Arch Linux 64-bit
Version: 7.1.0.0.alpha0+
Build ID: 8e4c79472644452431381733a5e4b21f98fcdcf3
CPU threads: 8; OS: Linux 5.7; UI render: default; VCL: kf5
Locale: fi-FI (fi_FI.UTF-8); UI: en-US
Calc: threaded
Built on 19 June 2020
Comment 2 QA Administrators 2022-09-29 03:54:48 UTC
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