Summary: | Set cursor to start in 'date' field in ledger view | ||
---|---|---|---|
Product: | [Applications] kmymoney | Reporter: | Nathan <npschwarz> |
Component: | general | Assignee: | KMyMoney Devel Mailing List <kmymoney-devel> |
Status: | RESOLVED FIXED | ||
Severity: | wishlist | ||
Priority: | NOR | ||
Version First Reported In: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Other | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | 5.2 | |
Sentry Crash Report: |
Description
Nathan
2024-03-03 22:36:56 UTC
What version of KMyMoney are you using, what distro or OS, and where did you download your copy? (Note that when filing a bug, the SOFTWARE/OS versions should be set to what you are using. Unless you have actually tested, setting any of then to "ALL" is not helpful.) This won't make any difference in this bug, but I point it out for future reference. In master branch, you can re-order the columns in the ledger, so saying left to right may not be the same for everyone. Also, for me, in master branch, creating a new transaction, the cursor does start in the date field. Unfortunately, this is not likely to get changed in the 5.1 branch. Unfortunately, there is still no definite timeline for releasing 5.2, which will be the first release from what is now the master branch in git. I suppose a further wishlist could be to let the user specify the tab order of fields in the ledger, but for now, I'll close as fixed. Jack Thanks for the quick reply. I am using version 5.1.3 from Kubuntu repos. But I understand its not relevant on this bug. I will be more detailed in future reports. I am glad to hear that the master branch does start in the date field. I think the column order of |Number| Date| Details| C| Payment| Deposit| Balance |in 5.1 is pretty standard. I don't know if re-ordering columns is necessary. But I can see where it might be a nice feature. However, even if you re-order the columns, I would still suggest that when starting a new transaction, the cursor should start in the first column on the left and work across the ledger. It wouldn't make sense to re-order the columns if you then needed to enter the data in a different order than the column order. I hope that makes sense. Thanks for listening to my request and all the work your doing on the project. Nathan On 3/3/24 17:48, Jack wrote: > https://bugs.kde.org/show_bug.cgi?id=482346 > > Jack <ostroffjh@users.sourceforge.net> changed: > > What |Removed |Added > ---------------------------------------------------------------------------- > Status|REPORTED |RESOLVED > Resolution|--- |FIXED > Version Fixed In| |5.2 > > --- Comment #1 from Jack <ostroffjh@users.sourceforge.net> --- > What version of KMyMoney are you using, what distro or OS, and where did you > download your copy? (Note that when filing a bug, the SOFTWARE/OS versions > should be set to what you are using. Unless you have actually tested, setting > any of then to "ALL" is not helpful.) This won't make any difference in this > bug, but I point it out for future reference. > > In master branch, you can re-order the columns in the ledger, so saying left to > right may not be the same for everyone. Also, for me, in master branch, > creating a new transaction, the cursor does start in the date field. > Unfortunately, this is not likely to get changed in the 5.1 branch. > Unfortunately, there is still no definite timeline for releasing 5.2, which > will be the first release from what is now the master branch in git. > > I suppose a further wishlist could be to let the user specify the tab order of > fields in the ledger, but for now, I'll close as fixed. > To shed some light on the master version: data entry for transactions will always happen form based in the ledger. The order of the columns has nothing to do with the order of the widget entries. The editor has been completely rewritten and since Jack mentioned "I suppose a further wishlist could be to let the user specify the tab order of fields in the ledger": Pressing Ctrl+Shift+T while in the editor provides just that. Keeping it as resolved in 5.2 |