On Wed, 21 Jun 2000, Dave Peticolas wrote:
> 3. The creation of a GnuCash database file that is a readable but
> incorrect in a non-obvious way. Such a problem may not be discovered
> for some time. Such a problem could be caused by a bug in GnuCash or
> by the user accidentally entering wrong data or performing an operation
> that was later determined to be undesirable (like deleting an account).
For fixing user errors, keeping a bunch of save versions around and going back
to find a good-enough one seems inelegant. What I'd really like is a good
infinite Undo facility, like Gnu Emacs gives me. Better yet, I'd like to be
able to make a mistake, close GnuCash, realize my mistake, reopen GnuCash, and
undo the mistake.
Could you use the log facility to provide this "eternal" undo?
You wouldn't have to create a 'save history' trail: less complexity, less
disk space. You could also get rid of the "Do you want to save the changes"
dialog that comes up when exiting GnuCash, and just save automatically. In the
rare case where I don't want to save, I'll just undo before exiting. (Since the
answer to the current dialog is almost always 'yes', the dialog has pretty low
efficiency.)
--
Gnucash Developer's List
To unsubscribe send empty email to: [EMAIL PROTECTED]
