Issue 112775 - Macro changes not saved on document Close/Save
Summary: Macro changes not saved on document Close/Save
Alias: None
Product: General
Classification: Code
Component: code (show other issues)
Version: OOO320m12
Hardware: All All
: P3 Trivial (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
Depends on:
Reported: 2010-06-29 01:33 UTC by r000000
Modified: 2013-01-29 21:46 UTC (History)
3 users (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---


Note You need to log in before you can comment on or make changes to this issue.
Description r000000 2010-06-29 01:33:31 UTC
Overview: Sometimes changes to a Macro, in either a Module or in a Dialog, are
not saved when the document is closed (with Save).

Analysis: This appears to happen if (1) the 'Save AutoRecovery information every
__ minutes' option (Options -> Load/Save -> General) is turned on and (2) an
auto-save action takes place prior to (a) Closing (with the Save option) or (b)
manually saving the document (e.g., File -> Save or ctrl-s).

1. Ensure the Save AutoRecovery option is turned on.  For convenience, set the
time value short, like 2 to 5 minutes.
2. Create a new document (spreadsheet and text documents have been tested). 
Create a Module (Module1 by default).  Save the document.  Optionally, open an
existing document that contains a Module.
4. Modify the Module (for example, add a comment).
5. Wait for the autosave action (indicated by a 'saving' message in the status
bar, which can be very quick in a simple document and thus difficult to see) or
wait at least as long as the autosave minutes option is set to.
6. Close (Save) the document).
7. Open the document.  Look at the Module.  (The change you made is probably not

This also occurs for Dialog changes.
This also occurs with previous versions of oo (2.0, 3.1.1 tested).  (I'd had
auto-save turned off while using version 2, so I didn't discover the problem for
some time.)
This occurs on at least Windows and on Linux.
Auto-save does save the changes.  This can be seen if the process is killed
(after auto-save takes place); the restore process, on the next OO startup,
shows the change.

Workaround:  (1) Turn off auto-save, or (2) execute a manual Save immediately
after changing a Module or Dialog.  (Probably still fails if the auto-save takes
place between the time you make the change and the time you save it, but that's
hard to confirm.)

Further notes and possible appologies:  I have no idea what subcomponent
applies, or even what the various options mean; since it's required, I merely
selected the first.  As a first time issue submitter, I find the process not as
straight forward as I might hope.
Comment 1 Olaf Felka 2010-06-29 06:48:05 UTC
@ jsk: Please have a look.
Comment 2 cno 2010-07-21 16:06:15 UTC
hi rkk

I can confirm the issue (Ubuntu)
Never stumbled over it, probably because I seldom work in document bound macro
Thanks for your first issue ;-)
Comment 3 hans_werner67 2011-03-28 11:58:16 UTC
Assign to new default-assignee
Comment 4 stfhell 2012-12-10 13:48:26 UTC
Problem still exists with AOO 3.4.1 (Ubuntu 12.04):

Edit Basic macro in an ODT, wait for auto-save, close Basic IDE without explicit save, save ODT. If you return to the Basic IDE, the changes are still there. But if you close and reopen the ODT, the changes are lost.
If you exit the Basic IDE before the auto-save and save the ODT, changes in macros persist.