Version: LibreOffice 3.3.2 - OOO330m19 (Build:202), Ubuntu package 1:3.3.2-1ubuntu4 The area transparency applied is rendered differently in design view and in presentation view. This is very annoying because colors looking perfect while designing appears very poor while presenting. The workaround for this is to use a gradient transparency very similar to the desired transparency (IE: for a desired transparency of 50% use a gradient between 50% to 51%). An example document is attached. This has also been reported and confirmed in this Ubuntu bug: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/768508
Created attachment 45928 [details] Test document
NOT reproducible with reporters sample document. "LibreOffice 3.3.2 – WIN7 Home Premium (64bit) German UI [OOO330m19 (Build:202 / tag 3.3.2.2)]". I can not find any significant difference in view between edit mode and presentation mode. @Fabian Rodriguez: Please do not use such rare terms like "differently", "perfect", "poor", "wrong", but describe exactly! A screenshot sometimes will say more than 1000 words ;-)
The effect is shown on <https://launchpadlibrarian.net/70123472/PresentationView.png> from mentioned ubuntu bug report. @Fabian Rodriguez: Still visible with 3.4Beta?
Might be Ubuntu specific or something else. Closing Bug due to reporter's inactivity as WFM. @reporter: Please feel free to reopen this bug if you find out that the problem still exists with the current LibreOffice version and if you can contribute requested additional information!
Might be related to or DUP of Bug 36547 - Impress: Rendering problems with some .odp files
Also Bug 33591 - Area transparency turns gray in presentation mode sounds similar
Hello Rainer, I'm the original bug reporter on Ubuntu. I've checked the Bug "33591 - Area transparency turns gray in presentation mode sounds similar" and I can confirm that this is duplicated of that one. Thanks in advance
Confirmed in Ubuntu 11.04, LibreOffice 3.4.0 DEV300m103(Build:5)
*** This bug has been marked as a duplicate of bug 33591 ***
*** Bug 36547 has been marked as a duplicate of this bug. ***
closing