Bug 332794 - Preferences Setting for Default Entry Style seems to be missing
Summary: Preferences Setting for Default Entry Style seems to be missing
Status: RESOLVED WORKSFORME
Alias: None
Product: kmymoney
Classification: Applications
Component: general (show other bugs)
Version: git (master)
Platform: Compiled Sources Linux
: NOR normal
Target Milestone: ---
Assignee: KMyMoney Devel Mailing List
URL:
Keywords: triaged
Depends on:
Blocks:
 
Reported: 2014-03-30 05:04 UTC by Michael T. Garrison Stuber
Modified: 2018-10-27 03:42 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Michael T. Garrison Stuber 2014-03-30 05:04:43 UTC
In KMM 4.6.4 and previous it was possible to change the default entry settings for security:
price per share or total for transaction

While this can still be set on per security basis, the system-wide default appears to be missing.

Reproducible: Always

Steps to Reproduce:
1. Go to investments
2. Pick a security.
3. Edit it.
4. Go to page two of the wizard and note the "price entry" field, which says "default"
5. Go to Configure->Configure KMyMoney
6. Look at ledger, data entry.  Don't find "price entry" option.
7. Look at every other tab and section under settings.
8. Scratch head in wonder.  
9. File bug.


Expected Results:  
Somewhere I should be able to set the price entry default.
Comment 1 Cristian Oneț 2014-09-24 11:27:43 UTC
The price mode was never editable while changing an existing security it was read only since the day it was added [1].

It can only be changed while the security is being created (it's fix after creation) [2]. I don't know the reason behind this restriction so if some good arguments for it's removal are provided we'll leave it as is for now.

Any thoughts on this?

[1] http://kmymoney2.cvs.sourceforge.net/viewvc/kmymoney2/kmymoney2/kmymoney2/dialogs/knewinvestmentwizard.cpp?r1=1.16&r2=1.17&

[2] http://docs.kde.org/stable/en/extragear-office/kmymoney/details.investments.securities.html#details.investments.newinvestmentwizard
Comment 2 Jack 2015-06-28 23:35:17 UTC
I just ran into this, and there does seem to be something strange going on.  

Given that the setting for an individual security has the choice of "(default)" "Price per share" or "Total for all shares", it seems it should be possible to set the overall default.  However, I'll accept that the default is "price pre share" and I can create a wishlist bug to allow changing it.

Cristian - I'm not sure why you point to the source from the old sourceforge respository, although it looks like that section of code is still pretty much the same.  However, I don't see that it shows the price mode can't be changed after creation.  I know that may just be my lack of familiarity with the code - but that "no chance to change" is under init2.  How does that differ from init1?

With the current version (from git, maybe a few weeks old) I CAN change the setting by editing an existing security, and it does change the behavior.  Unfortunately, it does NOT change the label on the entry field in the ledger - it still says "price/share" even though it does use the value as the total price for all shares.   I was hunting for any related bugs when I found this one.  The manual page you link to is just about creating an investment.  The next page, about editing an investment, does not give any details about whether or not you can change it later.  Perhaps I'll add some details to that page, once this issue is settled.
Comment 3 Jack 2015-06-28 23:48:38 UTC
Update: I've looked some more, and it seems there are two places you can set the price mode.  One is creating or editing the investment account.  The other is creating or editing an individual security.  For the security, it makes sense that the "default" refers the the choice for the account.  However, for the account, "default" seems to refer to a general, program level default, which is what cannot currently be set anywhere.  I would expect either to allow setting it (which could be a new wishlist) or to change the dropdown for the account from three choices to two:  "Price per share (default)" and "Total for all shares" since that choice reflects there is a real and unchangeable default.  It might also then be good to change the label for the security level setting from just "Default" to "Default for investment account".
Comment 4 Bob Ewart 2016-02-05 16:10:16 UTC
Setting the investment account to "Total for all shares" doesn't seem to do anything.  When a new security is automatically generated from an OFX import, it is set to "default" and is actually "Price per share".  

When a security is sold off, i.e. closed, Merrill Lynch sets the <TICKER> to the <UNIQUEID>.  This causes KMM to create a new security.  When the security is changed in the main broker account back to the original security, it takes the total as the price/share and generates a very large total, even though the original security and the account are both set to "Total for all shares".
Comment 5 Bob Ewart 2016-02-05 16:48:49 UTC
More on the above situation.  

As the new transaction comes in, the Shares, Price/share, Fee Amount and Total are correct.  When the security is changed back to the original one, it uses the Total as the Price/share no matter what the price entry is for the new security.
Comment 6 Andrew Crouthamel 2018-09-25 21:40:34 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 7 Andrew Crouthamel 2018-10-27 03:42:26 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!