Re: [GNC] Auto commit with auto save?

A little bit of a topic change, but I find setting Edit > Preferences > Scheduled Transactions > check box Review Created Transactions as an overall preference (as opposed to remembering to check the box on the popup scheduled transactions window) really simplifies scheduled transaction fixing

Re: [GNC] Auto commit with auto save?

On Sun, 7 May 2023 07:18:20 -0700 Stan Brown wrote: > On 2023-05-06 22:28, David T. via gnucash-user wrote: > > The app does throw a dialog onscreen when a user tries to save with > > an open transaction. Unfortunately, the message is generic, and a > > user is forced to look through the open

Re: [GNC] Auto commit with auto save?

An alternative proposal is to create data elements to allow auto-saving of both the modified and unmodified transaction of uncommitted changes, so if the file is reloaded, the uncommitted state is restored as it was at the time of the save.  Then auto save would ensure these uncommitted

Re: [GNC] Auto commit with auto save?

As for missed threads, I've taken to opening the message queue on the mail server directly before I reply, just to be sure I'm replying with useful information... ⁣ David T.​ On May 11, 2023, 07:20, at 07:20, Adrien Monteleone wrote: >David, > >I didn't notice when I replied, that this thread

Re: [GNC] Auto commit with auto save?

David, I didn't notice when I replied, that this thread broke (at least for me) and there were more detailed replies. Now that I see what the OP was encountering, I agree, SQL won't be a solution for anything not committed. Other than this special case, I'm not sure it would be a good idea

Re: [GNC] Auto commit with auto save?

Adrien, The issue as stated is specifically the loss of an uncommitted transaction, so an SQL back end won't help with that. If, however, that open transaction prevents an entire session from being saved, then your suggestion merits attention. I personally don't know about that, though; the

Re: [GNC] Auto commit with auto save?

The SQL backends will get you an instant auto-save, but only for committed transactions. (as far as I know) You still have to hit Enter or Tab-through to finish a transaction, at which point the file is auto-updated. (thus, save-on-commit) Regards, Adrien On 5/4/23 4:30 PM, David G. Pickett

Re: [GNC] Auto commit with auto save?

-user Sent: Monday, May 8, 2023 3:00 PM To: David G. Pickett Cc: gnucash-user@gnucash.org Subject: Re: [GNC] Auto commit with auto save? Yes, one can imagine that. I can imagine that it would be possible to add something like that into the get quotes function that already exists, but I'm

Re: [GNC] Auto commit with auto save?

That seems to cover it. I'm disappointed that the bug was posted six years ago and still hasn't been addressed. I know that the developers are far from idle, but to me it just seems so basic that you don't tell the user "There's a problem, now try to guess where it is." Stan Brown Tehachapi, CA,

Re: [GNC] Auto commit with auto save?

-Original Message- >From: David T. >To: David G. Pickett >Cc: David G. Pickett via gnucash-user >Sent: Sun, May 7, 2023 11:34 pm >Subject: Re: [GNC] Auto commit with auto save? > >Nope and nope. Sorry. > >It seems to me that leaving GnuCash open and running a con job a

Re: [GNC] Auto commit with auto save?

crontab. -Original Message- From: David T. To: David G. Pickett Cc: David G. Pickett via gnucash-user Sent: Sun, May 7, 2023 11:34 pm Subject: Re: [GNC] Auto commit with auto save? Nope and nope. Sorry. It seems to me that leaving GnuCash open and running a con job against the open

Re: [GNC] Auto commit with auto save?

From: David T. >To: David G. Pickett >Cc: gnucash-user@gnucash.org >Sent: Sun, May 7, 2023 1:28 am >Subject: Re: [GNC] Auto commit with auto save? > >I agree that it would be nice to have some visual cue that a >transaction has been edited but not saved; that would be us

Re: [GNC] Auto commit with auto save?

Any suggestions on a) how a shell script tells that the auto save is incomplete, b) even if it knew, what it could do about it? -Original Message- From: David T. To: David G. Pickett Cc: gnucash-user@gnucash.org Sent: Sun, May 7, 2023 1:28 am Subject: Re: [GNC] Auto commit with auto

Re: [GNC] Auto commit with auto save?

How about *Bug 686051* - Pending transaction edits get "lost" (edit ) On Sun, May 7, 2023 at 9:19 AM Stan Brown wrote: > On

Re: [GNC] Auto commit with auto save?

On 2023-05-06 22:28, David T. via gnucash-user wrote: > The app does throw a dialog onscreen when a user tries to save with > an open transaction. Unfortunately, the message is generic, and a > user is forced to look through the open tabs and try to figure out > which register holds this

Re: [GNC] Auto commit with auto save?

I agree that it would be nice to have some visual cue that a transaction has been edited but not saved; that would be useful. I'm honestly not sure why that hasn't been implemented. The app does throw a dialog onscreen when a user tries to save with an open transaction. Unfortunately, the

Re: [GNC] Auto commit with auto save?

"Don't do that!" does not prevent data loss from human error, which for this app behavior is too easy to create and not realize. If the commit was automatic every time you modified a transaction when the new state was valid, then I would not leave the tab in an uncommitted state, but that is

Re: [GNC] Auto commit with auto save?

David, Perhaps you could call it a work-around, but years ago I trained myself to never leave my computer without looking at the titlebar for that teltale asterisk before the filename, and saving the file if it is there. Then, if GnuCash complains about an unsaved transaction, I get a chance to

[GNC] Auto commit with auto save?

I often accidentally leave a transaction complete but with the cursor of that sheet still on the same line, so despite an aggressive auto save setting, such a transaction is not committed to the saved image.  Of course, if it is not in valid form, it cannot be committed!  But if the host goes