Those are good ideas.  One other thing we could do is to have GNUCash continuously update its files (database) on the fly and leave them in a state where a kill would not be catastrophic.  Quicken seems to do the same thing.  I think we should be able to handle a ctl-alt-backspace, or worse, a power failure with at worst, the transaction being entered in jeopardy.  During imports, a method must be devised to allow it to know whether or not to back out changes after restoring power (Tim's method below seems applicable).  Of course, one other reliable method is to periodically back up the files (Quicken does this every n exits - mine's set to 3).  That way, I get a "known good" backup from time to time.  Then, at worst, my data entry is limited to restoring to that last known good, often no more than three days ago.  With online banking, it makes the job pretty easy to go back a few days.  It seems to me that we're just talking about a good disaster recovery method.

On Mon, 2003-03-10 at 07:08, TIm Wunder wrote:
On 3/10/2003 8:54 AM, someone claiming to be Nigel Titley wrote:
> On Mon, 2003-03-10 at 13:39, Greg Troxel wrote:
> 
>>  Nope.  Just like there is no way for gnucash to stop you from
>>  unplugging your computer or turning it off.  Exiting gnome is
>>  outside the purvue of gnucash.  By the time gnucash gets told
>>  that gnome is going away, you have no more UI.
> 
> 
> One way out of this would be for gnucash to gain the ability to process
> its own log files on startup. If there existed log files which were more
> recent than the save date on the main data file, gnucash could offer to
> roll forward the missing transactions.
> 

Suppose the user edits or changes the gnucash data file externally, thus 
changing it's timestamp. What would happen?

Could the transactions get saved as tentative (or something) and at 
gnucash start the user asked if he/she wants to apply the changes?

Something like:
"There were unsaved transactions from your last session. What do you 
want to do?
[Apply] [Cancel] [Review]"

Apply would save the file legitimately.
Cancel would revert the changes
Review would bring up the list of transactions for editing in a register 
window (or windows)

Just a thought...

> I appreciate this needs some code writing... but it does address
> concerns raised several times on this list about the ability to recover
> lost work by applying the log files. I don't feel sufficiently at home
> with the gnucash code to offer to do this yet I'm afraid. Some time in
> the future possibly.
> 

Regards,
Tim


_______________________________________________
gnucash-devel mailing list
[EMAIL PROTECTED]
http://www.gnucash.org/cgi-bin/mailman/listinfo/gnucash-devel
--
Kevin Benton <[EMAIL PROTECTED]>
_______________________________________________
gnucash-devel mailing list
[EMAIL PROTECTED]
http://www.gnucash.org/cgi-bin/mailman/listinfo/gnucash-devel

Reply via email to