[kmymoney] [Bug 452692] Investment Performance by Account Only Owned
https://bugs.kde.org/show_bug.cgi?id=452692 Ralf Habacker changed: What|Removed |Added CC||ralf.habac...@freenet.de --- Comment #10 from Ralf Habacker --- Created attachment 175700 --> https://bugs.kde.org/attachment.cgi?id=175700&action=edit Screenshot from previous major version ( In the previous major version of kmymoney the column "Dividends paid out" is included in the associated report. -- You are receiving this mail because: You are the assignee for the bug.
[kmymoney] [Bug 452692] Investment Performance by Account Only Owned
https://bugs.kde.org/show_bug.cgi?id=452692 Ralf Habacker changed: What|Removed |Added Attachment #175700|0 |1 is obsolete|| --- Comment #11 from Ralf Habacker --- Created attachment 175702 --> https://bugs.kde.org/attachment.cgi?id=175702&action=edit Screenshot from previous major version (update) Screenshot from previous version updated with corrected date range -- You are receiving this mail because: You are the assignee for the bug.
when upgrades don't work with existing rc files
I have just merged Ralf's additions to the Payees chapter of the handbook about payee link matching. Everything worked fine with a newly compiled KMM, except I still didn't see "Open URL" in the context menu for a transaction. By email, Ralf told me I needed to remove/rename ~/.local/share/kxmlgui5/kmymoney/kmymoneyui.rc because it didn't have the newly required section. Renaming that file allowed the new context menu entry to show up - but oddly, after using it, and then closing KMM, a new version of kmymoneyui.rc did not appear. I'm just curious what (if anything) will eventually cause a new version of that file to appear? I'm also assuming that without the file, the program defaults to assuming it should use the latest version, of which it has an internal (or otherwise hidden) copy. Is there any way for the program to know (and warn the user) when this (or any other) rc file needs to be updated/replaced/...? It's not very user friendly to introduce a new feature, and then have it not work for a reason like this. Jack