Bug 355010 - Autofill Transaction Select Amount
Summary: Autofill Transaction Select Amount
Status: REPORTED
Alias: None
Product: kmymoney
Classification: Applications
Component: general (show other bugs)
Version: 4.7.2
Platform: Other Microsoft Windows
: NOR wishlist
Target Milestone: ---
Assignee: KMyMoney Devel Mailing List
URL:
Keywords: triaged
Depends on:
Blocks:
 
Reported: 2015-11-07 23:34 UTC by flywire
Modified: 2018-10-01 12:49 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description flywire 2015-11-07 23:34:29 UTC
When a record is selected the Amount field should be selected (ie highlighted) so that the user can accept or change without having to select first.

Reproducible: Always

Steps to Reproduce:
1. Autofill a transaction
2. The Amount is entered and the Amount field is active but the amount field is not selected
3. Select (ie highlight) the amount field
4. Enter new amount

Actual Results:  
The amount field is active but not selected

Expected Results:  
Select  (ie highlight) the amount field

While transactions often reoccur the amount frequently differs. This would allow more efficient data entry.
Comment 1 Ralf Habacker 2018-02-04 23:27:04 UTC
Steps to Reproduce:
1. Autofill a transaction
You are refering to enter a payee in the "from" field, for which a transaction  has already been entered ? 

2. The Amount is entered and the Amount field is active but the amount field is not selected

If yes, I cannot reproduce the mentioned issue with 4.8.1. After choosing the related transaction and pressing tab several times to get to the amount field, the amount value is completly highlighted.
Comment 2 flywire 2018-02-05 10:59:10 UTC
In retrospect I didn't describe this very well and it is too long ago to recall details of a feature that was not workable for me so I processed data entry out of the program. Let me explain it like this:

Efficient keyboard entry (without mouse) is critical. I have used Quickbooks so I'll demonstrate with an example using direct entry into the ledger using this image: https://7mile.work/wp-content/uploads/2013/03/credit-card-register22.png. Keystrokes are also very similar on the deposit/ withdrawal/ cheque/ invoice/ transfer form.

After a transaction is accepted new transaction form lines are generated with the current date the user is up to. The cursor is on Payee and user enters as much as is required to select the payee from a list. If enter is pressed the the record is accepted, alternatively the user can change the amount and press enter or tab around the other fields, including the splits and tax, and press enter or escape to finish the record. There are other keyboard shortcuts on the form too.

The process is the same for auto-fill except the Payee is already entered and the amount is selected so it can be changed, accepted or other details changed. (eg enter to except transaction at current date user is up to or a few keystrokes to change amount then enter to accept transaction.)

I realised the KMM fields are entered in a different order but the (old?) Quickbooks interface works with fields most likely to change being entered increasing the likelihood that other field data can be accepted first.

I'd be more than happy to collaborate on improving the data entry but I'd need a template to code it.
Comment 3 Andrew Crouthamel 2018-09-28 03:28:03 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 4 flywire 2018-10-01 12:49:46 UTC
Refer https://bugs.kde.org/show_bug.cgi?id=355010#c2