To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=83632
User mav changed the following:
What |Old value |New value
================================================================================
Status|STARTED |RESOLVED
--------------------------------------------------------------------------------
Resolution| |FIXED
--------------------------------------------------------------------------------
------- Additional comments from [EMAIL PROTECTED] Tue Dec 4 11:00:33 +0000
2007 -------
The real problem was that the error code ( in this case it is warning ) was not
reset on the SfxObjectShell, so the saving has always failed after it was set.
The VB-checking source code makes no problem here. It sets the warning, but that
is quite legal and works well after the real bug is fixed. Yes, currently the
warning is lost, but only in this scenario.
The part with catching of the exception has been integrated. Unfortunately the
filter source code is not ready for error transport even in case the error is
set on the storage. Changing this would affect all the MS-related filters, so I
would not like to do it for this issue.
---------------------------------------------------------------------
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]
