https://bugs.kde.org/show_bug.cgi?id=515398
--- Comment #5 from piedro <[email protected]> --- First, thank you all your attention! I wasn't used to bug reports getting responses so quickly... really appreciated! Also: I am sorry about the version numbers - "latest" is obviously not useful, won't do it again. Yes, I make backups - though for a program like kmymoney I think they are not that useful. Unless you basically save after every edited transaction... I use kmymoney in bursts of long hour sessions, going back to backup before the last session is really not feasible. But now I learned that there are hidden backups in the folder where the latest "*.kmy" file is saved. They seem to be created automatically - I love it. Rename the one from 5 minutes ago after messing up and, voila!, ready to go! Sadly in my case the two frozen transaction have been created some time ago without me noticing. Yes, in edit mode there is the drop down with these attributes. And here's the thing: Accidentally hovering the mouse pointer over the drop down for a brief moment while the mouse wheel is moving a tiny bit... That's enough to switch to a random attribute without even recognizing. Just close the editor mode and you already froze yourself out of the transaction. This happened to me quite a few times - most of the times a caught the setting before closing the transaction editor. So, yes, @jesse... There is no button nor warning. And I'd really like the idea of any kind of safe guard. It could also be just an opt-in setting that explicitly allows for the choice of "frozen" for this session. Maybe it's just me, but a password secured login to "unfreeze" mode to allow a user to at least unfreeze their own files. Or vice versa: if they decide to want to freeze something they might have to go into the settings page to allow "hardcore book keeping", then freeze some transactions and lock this feature again. There is many ways, depending on the intended purpose... which I don't fully get tbh. A warning that something irreversible is going to happen, if you proceed - that should be the minimum, imho. Thanks, @jack, for the instruction about the way to fiddle with the database. I think I will have to try that route next weekend. \_OO_/ Cheers, p. -- You are receiving this mail because: You are watching all bug changes.
