KWD has three decimal places. It all works well in the main pages. But when trying to split a transaction of, say KWD 16.575, in the split window the last 5 fils get rounded to zero. So, there is forever a warning that 5 fils have not been allocated. Reproducible: Always Steps to Reproduce: 1.Enter any amount, say, 16.575 or 48.840 (these are randomly picked amounts) 2.Split into any amount, where the split amount ends with 5 fils 3. Actual Results: If a split amount of, say, 10.075 is selected, it get deducted correctly from the intitial amount that will then show (correctly) 6.500, but the amount of the split is captured as 10.08 and not as 10.075. Expected Results: Expected result is 10.075. Since the problem does not occur on any of the main pages, it seems to me that it is merely a matter of allocating three, instead of two decimal place in the code for split window.
Created attachment 88060 [details] Test file that confirms this I can confirm this, the edit in the split editor might be missing a proper precision setup.
Created attachment 88061 [details] Split editor before entering
Created attachment 88062 [details] Split editor after entering
Fixing this should be easy.
Git commit 98df765f2cb5fcb2ee253d7ba7141a59b0cf7bed by Cristian Oneț. Committed on 19/08/2014 at 12:37. Pushed by conet into branch 'master'. Use the proper precision in the split table. We must have only a few users with a precision more than 2 otherwise this should have been catched a long time ago. M +5 -2 kmymoney/dialogs/kmymoneysplittable.cpp M +6 -1 kmymoney/dialogs/kmymoneysplittable.h M +1 -1 kmymoney/dialogs/ksplittransactiondlg.cpp http://commits.kde.org/kmymoney/98df765f2cb5fcb2ee253d7ba7141a59b0cf7bed
Git commit 49c06bbd56834f963f20dc7a96b2cb3bcff393b3 by Cristian Oneț. Committed on 19/08/2014 at 12:37. Pushed by conet into branch 'frameworks'. Use the proper precision in the split table. We must have only a few users with a precision more than 2 otherwise this should have been catched a long time ago. (cherry picked from commit 98df765f2cb5fcb2ee253d7ba7141a59b0cf7bed) M +5 -2 kmymoney/dialogs/kmymoneysplittable.cpp M +6 -1 kmymoney/dialogs/kmymoneysplittable.h M +1 -1 kmymoney/dialogs/ksplittransactiondlg.cpp http://commits.kde.org/kmymoney/49c06bbd56834f963f20dc7a96b2cb3bcff393b3
Created attachment 88317 [details] attachment-28798-0.html Thank you for sorting this out, Cristian. Regards, Rahiem Cristian Oneț schreef op 2014-08-19 om 15:41: > https://bugs.kde.org/show_bug.cgi?id=331638 > > Cristian Oneț <onet.cristian@gmail.com> changed: > > What |Removed |Added > ---------------------------------------------------------------------------- > Latest Commit|http://commits.kde.org/kmym |http://commits.kde.org/kmym > |oney/98df765f2cb5fcb2ee253d |oney/49c06bbd56834f963f20dc > |7ba7141a59b0cf7bed |7a96b2cb3bcff393b3 > > --- Comment #6 from Cristian Oneț <onet.cristian@gmail.com> --- > Git commit 49c06bbd56834f963f20dc7a96b2cb3bcff393b3 by Cristian Oneț. > Committed on 19/08/2014 at 12:37. > Pushed by conet into branch 'frameworks'. > > Use the proper precision in the split table. > > We must have only a few users with a precision more than 2 > otherwise this should have been catched a long time ago. > (cherry picked from commit 98df765f2cb5fcb2ee253d7ba7141a59b0cf7bed) > > M +5 -2 kmymoney/dialogs/kmymoneysplittable.cpp > M +6 -1 kmymoney/dialogs/kmymoneysplittable.h > M +1 -1 kmymoney/dialogs/ksplittransactiondlg.cpp > > http://commits.kde.org/kmymoney/49c06bbd56834f963f20dc7a96b2cb3bcff393b3 >
You're welcome.
Git commit 5131eaf3fa1c4dec7ca6a4d0dcb177d281e3fa57 by Christian Dávid, on behalf of Cristian Oneț. Committed on 19/08/2014 at 12:37. Pushed by christiand into branch 'add-onlinebanking'. Use the proper precision in the split table. We must have only a few users with a precision more than 2 otherwise this should have been catched a long time ago. M +5 -2 kmymoney/dialogs/kmymoneysplittable.cpp M +6 -1 kmymoney/dialogs/kmymoneysplittable.h M +1 -1 kmymoney/dialogs/ksplittransactiondlg.cpp http://commits.kde.org/kmymoney/5131eaf3fa1c4dec7ca6a4d0dcb177d281e3fa57
*** Bug 340079 has been marked as a duplicate of this bug. ***