topview/annotatedbackups

On demand backup add-on for LibreOffice which allows comments to be added to backup names

annotatedbackups's Issues

Bug: Any open tables or queries are not closed before snapshot: current edits of unsaved records are not part of the backup.

Forms are tested for open and then auto-closed, but Tables and Queries are not yet tested or closed. SO embedded DB (HSQLDB) record edits won't be saved if in open tables or queries. A fix is planned for v 1.5.12.

When multiple databases open which have open forms, Close all forms finds too many forms

When I have more than one database open and I try to do a backup of the current data base, the open form of the other database is found and I am ask if I want to close it.

It would be better to figure out if only the current database has any open forms.

Does not work if run from My Macros & Dialogs window

You can run this from these windows:

*** - LibreOffice Base
*** - LibreOffice Base: Database Form (in either Edit or normal modes)

But you can't run it from a My Macros & Dialogs window (the place where you view your BASIC code).

My Macros & Dialogs is not backed up.

BASIC code which is shared by one or more documents and located in My Macros & Dialogs is not backed up, even if it is called by this document. If this common code is damaged then this document will fail. So at a minimum a warning is probably in order to back that up and how. Also a method of backing it up to a shared backup directory is needed.

Unraveling oDoc for a Form broke non Base modules.

Think this is fixed now.

Dual boot timestamps differ

Dual boot linux/windows users may want to change the timestamp seconds delimiter to work with both systems, rather than either. (Windows does not allow a colon so we change it to an underline, and we keep the colon in linux for improved readability.)

Author's note: I don't do development in windows anymore, so don't feel the need to make it work 100% dual boot safe. So long as it works in linux and windows, that is good enough for me.) Therefore a fix is not planned for this.

Purge deletes incorrect files.

sPath needs work

sPath needs to get renamed to sSubDir or sBackupSubDir. And a check needs to be put in to:

a) make sure settings version is supported, or if not tell user how to upgrade setttings
b) make sure sSubDir or whatever we call it does not contain any slashes.

Doesn't check for open report designs

Auto-save and close any dirty Tables or Queries

Forms are already closed (with a save prompt if dirty) before the backup, but so far, I haven't been able to figure out how to do the same with Tables or Query windows. The best I can come up with is to detect them as open, and ask the user to deal with them appropriately (manually).

Anyway, found this documentation (with help from another guy), which once I understand it might help get this done.

Connected database is not backed up. A warning message needed for now, and then a procedure for this additional backup is also needed.

Embedded data is backed up. And the documentation says that you must back up non-embedded databases separately. But a caution would be helpful when connected databases are open, suggesting that this tool doesn't back that data up, and that that data needs to be backed up separately.