To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=60323





------- Additional comments from [EMAIL PROTECTED] Thu Feb  2 07:35:39 -0800 
2006 -------
One concrete case where this fix would have helped, and thus will help if
similar fixes are done in the future (after the fix for this issue) is the
stroke-opacity fix in Issue 42959.

If you have saved a document containing a chart with lines that have 100%
opacity (that is unfortunately also true for many default lines) in a version
prior to SRC680.m125, those file contain a stroke-opacity of 0% (wrong export).
If you load such a file in a version after SRC680.m128 (in which the fix for
Issue 42959 is contained) and save it to a different location, the chart will
not be loaded an saved again, so that you get a new file that still contains the
bug in the OLE chart object.

The ifx for Issue 42959 checks the version with which the chart was saved by
checking the container document's meta.xml (because the chart itself has no meta
information) which leads to the wrong assumption that the chart does not contain
the bug. Thus the stroke-opacity values are not adapted, and the lines will be
invisible (0% opacity means 100% transparent).

As a work-around, you can try to make sure that all charts are at least once
loaded before you re-save the file. In Calc, you can press F9 to update all
charts. In other applications I fear it only helps to activate each chart once
(double-click).

---------------------------------------------------------------------
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to