"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 not how it was devised. I leave because it looks fine. There is no indication of an uncommitted transaction I can see. In terms of human factors, one might go to another tab for information to complete a transaction, so we do not want to prevent the user leaving a tab with an uncommitted, possibly invalid transaction. Maybe we should color the tab red while in this state? Or pop up a dialog if it persists a bit too long, or if auto save fires on its timer? But the user may have left, trusting in auto save, so I suggest an auto commit if valid on auto save. _______________________________________________ gnucash-user mailing list [email protected] To update your subscription preferences or to unsubscribe: https://lists.gnucash.org/mailman/listinfo/gnucash-user ----- Please remember to CC this list on all your replies. You can do this by using Reply-To-List or Reply-All.
