Selecting to include a category in the tax report by marking the checkbox in the account dialog presents a check mark in the category view. Turning off the feature by unselecting the checkbox in the account dialog does not remove the check mark in the category view. Reproducible: Always Steps to Reproduce: 1. Select category in category view 2. Edit it and select the 'Include on tax report' option. Save the settings 3. Edit the same category again and switch off the 'Include on tax report' option. Save the settings Actual Results: Category view still shows the check mark in the Tax column Expected Results: Category view shall not show the check mark in the Tax column This should also be fixed in the 4.7 branch.
Git commit cf16426575844043c6b1c4638e22582e0c799d1f by Thomas Baumgart. Committed on 05/10/2014 at 09:00. Pushed by tbaumgart into branch 'master'. Update model completely when account data changes Selecting to include a category in the tax report by marking the checkbox in the account dialog presents a check mark in the category view. Turning off the feature by unselecting the checkbox in the account dialog did not remove the check mark in the category view. This fixes the behavior. M +14 -7 kmymoney/models/accountsmodel.cpp http://commits.kde.org/kmymoney/cf16426575844043c6b1c4638e22582e0c799d1f
*** Bug 340214 has been marked as a duplicate of this bug. ***
Git commit 03f4c27a29f5fc6427f48344d013a4ae966400b4 by Cristian Oneț, on behalf of Thomas Baumgart. Committed on 05/10/2014 at 09:00. Pushed by conet into branch '4.7'. Update model completely when account data changes Selecting to include a category in the tax report by marking the checkbox in the account dialog presents a check mark in the category view. Turning off the feature by unselecting the checkbox in the account dialog did not remove the check mark in the category view. This fixes the behavior. (cherry picked from commit cf16426575844043c6b1c4638e22582e0c799d1f) M +14 -7 kmymoney/models/accountsmodel.cpp http://commits.kde.org/kmymoney/03f4c27a29f5fc6427f48344d013a4ae966400b4
The fix will be available in 4.7.1.