First of all many thanks for releasing the new version 5.2 after the long time since release 5.1. Very good to see so much activity.
When adding a new transaction, I enter the number of shares into “Shares” and the total amount into “Transaction amount”. This all works well. But when editing an already existing investment “Transaction amount” shows the value of one single share (“Price” in the table).
From my point of view here should be always displayed the total amount of all shares.
This applies for an investment account.
Bug 509454 created.
Hello,
to be honest, I lost track of all the versions and AppImages I used and tested over the last weeks. So I can’t say for sure if this commit worked for me any time. In the current AppImage of 5.2 it does not work. But looking at the linked line 140: shouldn’t the assignment be the other way round?
No, the variable price on the left of the assignment always needs to contain the price of a single share here. Therefore, the value in the widget can be taken as is in case the priceMode() of the security is PricePerShare and must be divided by the number of shares in case of PricePerTransaction. Hope that explains it.
Thanks for clarification, got this point.
But, however, the problem described in the initial post still persists (for kmymoney-5.2-4845-linux-gcc-x86_64.AppImage).
This commit was missing in the 5.2 stable branch but was present in master since late July. Since developers love to live on the bleeding edge (master branch) … 
It should now be part of build 4846.
Same with kmymoney-5.2-4848-linux-gcc-x86_64.AppImage.
The text “Transaction amount” is correct and is accordant to the settings of the investment. The amount is not correctly calculated, it is still the price per share. To illustrate:
I am unable to duplicate this here 
I have an existing transaction where the security is setup to use the default price mode. I edit it in the ledger (1) and see the price per share. Then I close the editor, change the price mode to total amount and open the transaction in the ledger again for editing (2).
I have a gut feeling that it has something to do with rounding problems and is specific to your values.
BTW: ran those tests with the same appimage as you.
Should now be fixed in build 4851
