Op woensdag 1 mei 2019 21:01:19 CEST schreef Adrien Monteleone: > > On May 1, 2019, at 1:40 PM, Geert Janssens <geert.gnuc...@kobaltwit.be> > > wrote: > > > > > > > > For what it's worth all business accounting packages I have used in > > Belgium > > protect the full transaction once reconciled. There's not a single field I > > can still change. > > Even on paper, I was taught to do all accounting in ink and make correcting > entries to fix errors. No editing or erasing was allowed. > > A strict implementation of this would be possible since GnuCash already has > the ‘reverse transaction’ feature, but I doubt many would be happy with > that move. > > If this were a corporate accounting package, that would probably be a > necessity. (and likely address, though not solve, many questions of > ’security’ some people have from time to time on the list - hey, look, > another option!) > > I have no hard opinion on what is best or how to best tackle this to work > > for most people. Though I think getting a warning you're about to alter a > > reconciled transaction should not be that bad. It prevents accidental > > changes and still allows deliberate changes (which currently require a > > reconcile). > > > > What we could perhaps do is this: keep the warning pretty strict, but only > > undo reconciliation if the change would alter the reconciliation balance > > (either a date change causes the transaction to fall outside of the > > reconciliation period is was in or the amount was changed). And document > > clearly what gnucash does. > > Not sure which would be easier, fire the warning on one set of criteria, but > only clear the flag based on a subset, or fire the warning for everything, > but only clear the flag if there is a boolean option in the dialog set to > do so. (checked by default, or implemented as action buttons) > > I would think the latter would involve less code, or at least less testing > of criteria, thus a little cheaper. (I’m aware things that look cheap for > code, aren’t always, but it sure looks that way abstractly to me for now)
It's one of those cases... The dialog that's currently used to pop-up the "change a reconciled transaction" is a generic one that's used for all the warnings we have. And that generic dialog has no provision for an extra boolean option. So if we want to go that route that means creating a separate dialog specifically for this use case. In addition the choice the user makes in this dialog has to be stored. Again this is one common method for all warnings. Adding a boolean option means we have to special case the storage of this warning. Having said all that perhaps giving the user the choice is wiser after all in this case. Regards, Geert _______________________________________________ gnucash-user mailing list gnucash-user@gnucash.org To update your subscription preferences or to unsubscribe: https://lists.gnucash.org/mailman/listinfo/gnucash-user If you are using Nabble or Gmane, please see https://wiki.gnucash.org/wiki/Mailing_Lists for more information. ----- Please remember to CC this list on all your replies. You can do this by using Reply-To-List or Reply-All.
