Shape's line properties are exported to PPTX files, but it seems the transparency value is not. Transparency value is supported by MSO.
Steps to Reproduce:
1. Open attached ODP with transparent line
2. Save it to PPTX file
3. Open the file with LO or MSO
Line transparency is gone.
Line transparency should be save to PPTX file.
User Profile Reset: No
User-Agent: Mozilla/5.0 (Windows NT 6.3; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/60.0.3112.90 Safari/537.36
Created attachment 135532 [details]
Test document with transparent line
Build ID: ef2e6260fad38e26c8591ea88ded348db618270d
CPU threads: 4; OS: Linux 4.10; UI render: default; VCL: gtk3;
Locale: ca-ES (ca_ES.UTF-8); Calc: group
Build ID: c15927f20d4727c3b8de68497b6949e72f9e6e9e
is the problem the same as in bug 91668?
> is the problem the same as in bug 91668?
I don't think that. Line properties and image properties are handled separately.
Let's turn it into a easy hack. The code is here:
Check DrawingML::WriteOutline(...) method
I looked into the code and was unfortunate to find anything related to transpaency in this function. It will be very helpful if I can get a little help in this matter.
Some more code pointers:
PPTX export code uses UNO API to get properties from the document modell. Line API properties are defined here:
These properties are get by GetProperty() calls. This GetProperty() method sets the property to the mAny variable from which you can convert the actual value to the right type (see other parts of the drawingml.cxx file how it works). So with this GetProperty() you can get the actualy line trasparency for the current object.
About how to export the transparency value you should check WriteSolidFill() method which is called from WriteOutline() method. It has an nAlpha paramter which is a kind of transparency value.
A polite ping, still working on this bug?
Tamás Zolnai committed a patch related to this issue.
It has been pushed to "master":
tdf#111786: PPTX export: Shape's line transparency is not exported
It will be available in 6.1.0.
The patch should be included in the daily builds available at
http://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More
information about daily builds can be found at:
Affected users are encouraged to test the fix and report feedback.