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


User nn changed the following:

                What    |Old value                 |New value
================================================================================
                      CC|'jbfaure,md,mru,rcaron'   |'jbfaure,mav,md,mru,nn,rca
                        |                          |ron'
--------------------------------------------------------------------------------




------- Additional comments from [email protected] Mon Apr 12 15:46:38 +0000 
2010 -------
Calc relies on notification of SFX_EVENT_SAVEDOCDONE or SFX_EVENT_SAVEASDOCDONE
after saving, to update the stream positions of individual sheets in the
content.xml stream of the document's storage (this is needed to distinguish from
saving for AutoRecovery, which doesn't modify the document's storage). But for
the embedded Calc object, the events aren't notified after saving. This causes
an error when saving the second time.

Issue 110692 is related to this, but not the same: There, the stream from the
document's storage can't be opened, so I didn't look for the notification until 
now.

The change in DEV300m68 was the fix for issue 106854 (directly using the
document's storage instead of opening it from its URL).

mav: Is the missing notification for embedded objects intentional? We could then
disable partial saving for embedded objects.

---------------------------------------------------------------------
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