[kmymoney] [Bug 489812] Kmymoney 5.1.3 stuck at splash screen
https://bugs.kde.org/show_bug.cgi?id=489812 Jack changed: What|Removed |Added Resolution|FIXED |NOT A BUG -- You are receiving this mail because: You are the assignee for the bug.
Re: extremely annoying failure
On Samstag, 6. Juli 2024 01:42:28 CEST Jack via KMyMoney-devel wrote: > First, I'll say there was no actual data loss, just loss of more time > than I'm happy losing over the past two days. > > On 30 June, I saved and backed up my data file, and began my end of > month reconciliation of my investment accounts. Yesterday, I had > completed reconciliation of one account. I thought I had saved, but in > retrospect (i.e., looking at available files) obviously not, and that > was my fault. > > Today, I completed reconciliation of a second account, and again > (unusually) neglected to save the file. > > I then started on a third account. These are all investment accounts, > and my broker sends two transactions for a dividend reinvestment. In > the Investment account, I convert one to a reinvestment transaction. > The other transaction only appears as a deposit in the brokerage > account. In this case, I reconciled the investment account first, and > then went to the brokerage account. I reconciled the account before I > deleted three of those "extra" transactions, which left me with an > incorrect balance, too large by the sum of those three transactions. > When I saw this, I deleted those three transactions, and only then > noticed the "wrong" reconciled balance. > > OK - I figured I could undo several steps, going back to right before I > did the reconciliation. Well, I did undelete those three transactions, > but at that point, the "undelete" button appeared disabled. I could > push it, and the window re-displayed, but nothing changed. Multiple > further presses did not remove the "now wrong" reconciliation banner > from the ledger. > > Is reconciliation not able to be undone, or have I discovered an actual > bug? That could well be. The reconciliation process is not a single action to be undone but many more. First you start the reconciliation, then you process the transactions (modify them, merge them, etc.) and then you finish it. Each of these steps is a single undo action (at least with the current implementation). > Unfortunately, I neglected to save a copy of the file in it's "bad" > state, although I can probably recreate it if necessary. > > Any thoughts? To analyze this further, a sample file with some detailed instructions would be extremely helpful. Not sure, if the undo/redo feature is really something we want to keep available in it's current state for the regular user. Given your example and description this could open a few large cans of worms for a regular user. We could hide it and only make it available as experimental feature in the next release. Thoughts? -- Regards Thomas Baumgart - Stay away from negative people. They have a problem to every solution! -- Albert Einstein - signature.asc Description: This is a digitally signed message part.
Re: extremely annoying failure
On 7/6/24 11:22 AM, Thomas Baumgart via KMyMoney-devel wrote: On Samstag, 6. Juli 2024 01:42:28 CEST Jack via KMyMoney-devel wrote: First, I'll say there was no actual data loss, just loss of more time than I'm happy losing over the past two days. On 30 June, I saved and backed up my data file, and began my end of month reconciliation of my investment accounts. Yesterday, I had completed reconciliation of one account. I thought I had saved, but in retrospect (i.e., looking at available files) obviously not, and that was my fault. Today, I completed reconciliation of a second account, and again (unusually) neglected to save the file. I then started on a third account. These are all investment accounts, and my broker sends two transactions for a dividend reinvestment. In the Investment account, I convert one to a reinvestment transaction. The other transaction only appears as a deposit in the brokerage account. In this case, I reconciled the investment account first, and then went to the brokerage account. I reconciled the account before I deleted three of those "extra" transactions, which left me with an incorrect balance, too large by the sum of those three transactions. When I saw this, I deleted those three transactions, and only then noticed the "wrong" reconciled balance. OK - I figured I could undo several steps, going back to right before I did the reconciliation. Well, I did undelete those three transactions, but at that point, the "undelete" button appeared disabled. I could push it, and the window re-displayed, but nothing changed. Multiple further presses did not remove the "now wrong" reconciliation banner from the ledger. Is reconciliation not able to be undone, or have I discovered an actual bug? That could well be. The reconciliation process is not a single action to be undone but many more. First you start the reconciliation, then you process the transactions (modify them, merge them, etc.) and then you finish it. Each of these steps is a single undo action (at least with the current implementation). The way I do it, it should be a bit simpler than that. I generally do all my "preparation" work first, then I hit the "Reconcile" button, adjust the date if necessary (in this case, changed from 30 Jun to 28 Jun) and click OK. I then click "Finish" which I have added to the toolbar. Unfortunately, I neglected to save a copy of the file in it's "bad" state, although I can probably recreate it if necessary. Any thoughts? To analyze this further, a sample file with some detailed instructions would be extremely helpful. I'll try to create one. Not sure, if the undo/redo feature is really something we want to keep available in it's current state for the regular user. Given your example and description this could open a few large cans of worms for a regular user. We could hide it and only make it available as experimental feature in the next release. Thoughts? No strong opinion. In this case, if I could have reversed the "finish" process, I could then have deleted the transactions and then hit "finish."One thing I have considered asking for as a wishlist is to be able to see a list of the queued up possible "undo" actions. For example, hovering over the Undo button might show a tooltip of the single action to be undone. However, keeping it hidden behind the "experimental" configure time flag is reasonable.
[kmymoney] [Bug 273335] Wishlist- Ledger view - change item order
https://bugs.kde.org/show_bug.cgi?id=273335 Jack changed: What|Removed |Added Version|SVN |git (master) Platform|openSUSE|Compiled Sources --- Comment #1 from Jack --- Given this is still an issue, I've updated some of the details. However, I don't see any reasonable way to adjust the order of individual transactions, unless we add a new field to each transaction, as I do not think we want to change one of the current date fields to date/time. The new field could be date/time, just a time, or perhaps just a "sort" integer. This field would use a default value for most transactions, but be editable to slightly order the sort within a day. It might make sense to only allow sorting by this field after one of the date fields. -- You are receiving this mail because: You are the assignee for the bug.
[kmymoney] [Bug 253530] in ledger view the cursor moves to wrong position after selecting the Transfer or Withdrawal tabs
https://bugs.kde.org/show_bug.cgi?id=253530 --- Comment #6 from Jack --- Given it's been a long time, and I don't know if the OP is still using KMM, but I wonder if this is still a problem with the new ledger code in git master? I also wonder if we have an open wishlist to alter the tab order of fields in the ledger, which might also be helpful here. -- You are receiving this mail because: You are the assignee for the bug.
[kmymoney] [Bug 474917] Text reports are gray with no information
https://bugs.kde.org/show_bug.cgi?id=474917 --- Comment #14 from Jack --- I'm not sure if anything was explicitly done about this, but I wonder if we should close it as fixed in 5.2? -- You are receiving this mail because: You are the assignee for the bug.
[kmymoney] [Bug 342401] allow different payees on splits
https://bugs.kde.org/show_bug.cgi?id=342401 --- Comment #12 from Jack --- If I'm not mistaken, this is now possible in the new ledger, used in any version compiled from git master. It would be great if the OP could confirm it works for him, and we could close as fixed in 5.2. -- You are receiving this mail because: You are the assignee for the bug.
[kmymoney] [Bug 442354] When matching transactions, the first one selected should be first shown in the "Merge Transactions" dialog
https://bugs.kde.org/show_bug.cgi?id=442354 --- Comment #2 from Jack --- Hasn't this been addressed in the new ledger? It is now possible to switch which transaction is considered "first" when merging. If someone else can confirm, I'll be happy to close as fixed in 5.2. -- You are receiving this mail because: You are the assignee for the bug.
[kmymoney] [Bug 317511] Allow transaction editing from ledger view after double-clicking on category in category list
https://bugs.kde.org/show_bug.cgi?id=317511 --- Comment #7 from Jack --- Are we ready to call this closed and fixed in 5.2? -- You are receiving this mail because: You are the assignee for the bug.
[kmymoney] [Bug 454485] KMyMoney crashed when opening a ledger
https://bugs.kde.org/show_bug.cgi?id=454485 Jack changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #3 from Jack --- Given that gnutls has likely been upgraded since this was reported, and you should now be using KMM 5.1.3, does this still happen? -- You are receiving this mail because: You are the assignee for the bug.
[kmymoney] [Bug 451828] When importing Online transactions using OFX, transactions may be skipped if occurred on the day of the last update
https://bugs.kde.org/show_bug.cgi?id=451828 Jack changed: What|Removed |Added Resolution|--- |WORKSFORME Status|REPORTED|RESOLVED --- Comment #6 from Jack --- I tend to blame such things on the phase of the moon. I'm not suer why this wasn't closed but doing so now. Obviously this can be reopened if the problem recurs. -- You are receiving this mail because: You are the assignee for the bug.
[kmymoney] [Bug 441793] Phantom Transaction
https://bugs.kde.org/show_bug.cgi?id=441793 Jack changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #1 from Jack --- I"m not sure why this never got addressed, but unless you still have a data file that shows this problem, I'm tempted to close this as WORKSFORME. -- You are receiving this mail because: You are the assignee for the bug.
[kmymoney] [Bug 419570] Provide split category detail instead of fixed text 'Split transaction'
https://bugs.kde.org/show_bug.cgi?id=419570 Jack changed: What|Removed |Added CC||ostroffjh@users.sourceforge ||.net --- Comment #2 from Jack --- Hasn't this been addressed in the new ledger in git master? -- You are receiving this mail because: You are the assignee for the bug.
[kmymoney] [Bug 489451] When buying stocks with precision>2, the rounding rule used in the ledger is wrong
https://bugs.kde.org/show_bug.cgi?id=489451 --- Comment #4 from Thomas Baumgart --- Created attachment 171438 --> https://bugs.kde.org/attachment.cgi?id=171438&action=edit Rounding in current master version This has been corrected and is working properly in the master version. See attached screenshot showing the edit widgets on top and the ledger entry at the bottom. -- You are receiving this mail because: You are the assignee for the bug.
[kmymoney] [Bug 489451] When buying stocks with precision>2, the rounding rule used in the ledger is wrong
https://bugs.kde.org/show_bug.cgi?id=489451 Thomas Baumgart changed: What|Removed |Added Resolution|WAITINGFORINFO |FIXED Status|NEEDSINFO |RESOLVED Version Fixed In||5.2 --- Comment #5 from Thomas Baumgart --- Resolved as per previous comment -- You are receiving this mail because: You are the assignee for the bug.
[kmymoney] [Bug 253530] in ledger view the cursor moves to wrong position after selecting the Transfer or Withdrawal tabs
https://bugs.kde.org/show_bug.cgi?id=253530 Thomas Baumgart changed: What|Removed |Added Resolution|--- |FIXED Version Fixed In||5.2 Status|REPORTED|RESOLVED --- Comment #7 from Thomas Baumgart --- This is most likely outdated. The git master version contains a tab order editor to customize the tab order in the transaction editors. Edit or create a transaction and press Ctrl+Shift+T. -- You are receiving this mail because: You are the assignee for the bug.
[kmymoney] [Bug 317511] Allow transaction editing from ledger view after double-clicking on category in category list
https://bugs.kde.org/show_bug.cgi?id=317511 Thomas Baumgart changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED Version Fixed In||5.2 -- You are receiving this mail because: You are the assignee for the bug.
[kmymoney] [Bug 419570] Provide split category detail instead of fixed text 'Split transaction'
https://bugs.kde.org/show_bug.cgi?id=419570 Thomas Baumgart changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED Version Fixed In||5.2 -- You are receiving this mail because: You are the assignee for the bug.
[kmymoney] [Bug 342401] allow different payees on splits
https://bugs.kde.org/show_bug.cgi?id=342401 Thomas Baumgart changed: What|Removed |Added Status|CONFIRMED |RESOLVED Version Fixed In||5.2 Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[kmymoney] [Bug 488480] Auto Reconcile not working
https://bugs.kde.org/show_bug.cgi?id=488480 --- Comment #2 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are the assignee for the bug.
