Hi everyone,
I’m experiencing an annoying behavior in the ledger view.
When I enter an amount using the numeric keypad, the cursor correctly stays inside the input field, but the view automatically scrolls to the first transaction with a date starting with that number. For example, if I press “1”, the ledger jumps to the first entry of the month (or year) starting with 1.
Since my ledger contains hundreds of transactions, the view scrolls away and I can no longer see the entry I am currently editing.
Is there a way to disable this “jump to date” shortcut or prevent the ledger from scrolling while I’m typing in the amount field?
I have never experienced that ‘feature’ nor do I know that someone has deliberately coded it 
It seems to be some sort of misbehavior of the application which is yet unknown. In order to troubleshoot it, please provide at least the following details:
- Operating System
- KMyMoney Version (from Help/About dialog)
- Where did you get that from?
Once we have those, we might come up with more questions.
You are absolutely right. Here are the details you requested:
Note: I recently reported another bug which was fixed in record time, thank you for that!
Ledger View Columns: Date, Details, Payment, Deposit, Balance.
Steps to reproduce:
-
Go to a ledger with hundreds of entries.
-
Press CTRL+INS (or click at the bottom) to create a new transaction.
-
Move the cursor/focus to the Payment or Deposit field.
-
Press “1” on the keypad.
Observed behavior: The ledger immediately jumps to the first entry with a date starting with “1” (e.g., 10/10/2002). The cursor actually remains inside the Payment/Deposit field, but since the ledger has scrolled all the way up to the year 2002, the current transaction I’m editing is pushed off-screen.
The same happens pressing “2”: it jumps to the first entry starting with “2” (e.g., 20/10/2002).
I hope this clarifies the issue. Thank you for your help!
I could not duplicate that behavior with my Fedora installation (KMM 5.2.1 from FLatpak).
In my case, it works as expected. If I turn off numlock the cursor does not move and no numbers are printed. I tried both the Deposit and Payment fields. hth. A
I have some further updates that confirm this is likely a Windows-specific issue related to how the numeric keypad is handled.
-
The Cause: I confirmed that the issue only occurs when NumLock is ON. When NumLock is OFF, the “jump to date” behavior stops.
-
The Behavior: It appears that when NumLock is active, the keypad input is intercepted by the Ledger’s navigation logic (incremental search) as if I were clicking directly on the list, even though the cursor is technically inside the input field.
My Workaround: Since I don’t use the “Number” (No.) column for my transactions, I moved it to be the first column on the left of my ledger. Since this column is empty for all my entries, the incremental search finds no matches when I type a number, and therefore the view no longer jumps away.
While this workaround works for me, it confirms there is a focus/input handling bug in the Windows version when using the numeric keypad.
CONCLUSION
Even though I found a workaround by rearranging the columns, this is clearly a bug in the Windows version. The numeric keypad is essential for fast accounting data entry, and having the focus “leak” from the input field to the ledger navigation is a significant UX issue.
I hope these details help the development team identify why the NumLock input is being intercepted.
Should I open a formal ticket on bugs.kde.org with this information, or is this thread sufficient for the team to track the issue?
Thanks again for the support!
@Mauro_Rog Can you try the latest Windows master build and report if the problem persists or not? Thanks in advance.
Reason: Some substantial changes have been added around the numeric keypad handling in the amount widget after your report here.
Sorry for the delay in responding.
The version you recommended solved the problem.
Thanks again for your help.
No problem. We all do this on our spare time. Thanks for the feedback.