I believe that this fault may have been reported before but it is still happening. In a purpose-written CALC spreadsheet (*not* translated from XLS), I have written a number of macros - both functions and subs. On several occasions I have gone into the macros, edited them, closed the macro editor, exited and saved the file and when I re-open the file at a later time (same day or even later) the changes to the macros have not been saved. This is happening more than 50% of the time and is extremely annoying. I always carry out the same sequence of events on completion - close/exit/save. I am using Ubuntu 12.04, LibreOffice 3.5.3.2 Build 350m1 (Build:2) I am unable to supply files that this happens with as it does not happen *every* time
See bug report 42899 also
Please can we get a sample of at least one file where this happens for you
Sorry - cannot do that. 2 reasons - 1 is (as I described in my initial comment) this does not happen every time that I do an edit and (2) the information in the macros is commercially sensitive Sorry I can't be more help but hopefully more people will be able to replicate the bug somewhere in OpenOffice-land and provide meaningful information. I have seen a bug report elsewhere (from a Japanese user?) that was having the same problem.
This has been reported before and I have made comments on it. Making a test case is hard as the saves don't happen so I'm not sure what test document we would provide. The issue is that if you save in a certain way things work fine every time, to do this: a) Edit macro b) COMPILE macro c) save macro within editor d) save document I think the issue comes when you do this: a) edit macro b) close editor c) save document I have been unable to confirm this as I've been pretty busy on other projects lately but this IS a problem if it still exists. Someone needs to pinpoint the exact steps that a user does that makes it so macros do not save, if they are reproducible every time, we can fix it. I personally have seen this and lost a great deal of work because of it, so I know it can be frustrating but we need people to test exactly when it saves and when it doesn't. @ADB, if you want, email me directly and we'll work out test cases. It shouldn't take long just like I said, I've been swamped with LO stuff on top of my regular job ;)
I'm marking this as a DUPLICATE of the previously mentioned bug (42899). Please help get the steps together so we can actually solve this problem, I'm also changing status of other bug to NEEDINFO as the information just isn't there for a developer to fix the problem *** This bug has been marked as a duplicate of bug 42899 ***