Created attachment 113587 [details] Number field too narrow for 3 digits The number field is too small when entering transactions directly into the list. Currently only two characters are visible in the number field but at least three should be visible if not 4. See the attached screenshot where I have entered the number 111 but only "11" is visible. Steps to reproduce: 1. Turn off transaction form (Settings->Configure KMyMoney->Ledger->Display tab). 2. Insert a new transaction in an account 3. See that only two characters are visible in the Number field.
I believe this is working as designed. Initially, the number field starts out with 2 digits probably based on the assumption that you'll begin with a single digit (ie 1). As you enter more digits the No. field grows based on the actual number of digits that are inputted. I entered 30 digits (I stopped there) and the field actually grew 30 digits wide.
Created attachment 113615 [details] Input field clips to smaller than column display I notice that the numbers display column does expand when the transaction is entered, but the input field for the number is about one digit smaller than the display. To show this, I entered a big number for a transaction (in this case 1234567) and the number column resizes after entering the transaction. In the next transaction I type in the number to 1234568, but the input field only displays the last 6 digits instead of all 7 (the leading digit is clipped in the view but still there). I'll attach another screen shot here to demonstrate. This is independent of how wide the KMM window is. I feel that the input field should be able to show the same number of digits as the column displays when not editing the transaction, and it looks like it may be a regression from whenever the screen shot on this page was taken: https://docs.kde.org/stable5/en/extragear-office/kmymoney/details.ledger.direct.html. I figured it should be reported as a bug due to that (although probably a rather minor bug).
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version? If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
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 mark the bug 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!
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!