https://bugs.kde.org/show_bug.cgi?id=493802
--- Comment #8 from Jack <ostrof...@users.sourceforge.net> --- Sorry for any confusing terminology. When reporting the version you are using, it helps state what Help/About KMyMoney says. In this case, it wouldn't have actually mattered, but the full version would have told us you were using the Appimage and not a version released by the distribution. (You would have to include that in the report, as the dropdown for versions does include "git(master)" but not a way to say git(stable) or git(5.1). Code development is done in git, in which there are different "branches" which allows multiple lines of development to be tracked. The 5.1 branch has the code for 5.1.3, and includes bug fixes. The Appimage versions compiled from the code in the 5.1 branch will have versions like kmymoney 5.1.3-eef04f1 where that last bit shows the exact "commit" (specific change) included. The "master" branch includes additional bug fixes, plus new features. In this case, one of the major changes is a major rewrite of the ledger code. Versions from master branch look like kmymoney 5.1.80-fd13f44. The code from master branch will be released as 5.2, but there is not yet a definite timeline for that. Given that your two main problems have been addressed there, I will close this as resolved in 5.2. Although using master branch is labelled as experimental, there are multiple folks who have been using it for their day-to-day work. The only special advice is be sure to keep good backups. I'm not absolutely certain, but I believe that the change of display color for the balance of liability accounts is intentional. Since they are LIABILITY accounts, a positive amount (shown in black) is what you owe. While you could open a wishlist bug requesting it be changed back, or made a configuration choice, I do not suspect it will get much priority. -- You are receiving this mail because: You are the assignee for the bug.
