SUMMARY When looking for old operations, the lookup is made in a child window that does not allow operation inspection, modification. STEPS TO REPRODUCE 1. Lookup for an old operation 2. Try to have a deep look at its properties OBSERVED RESULT It's not possible to have a look at the operation properties EXPECTED RESULT It should be possible to have a look at the operation properties and event modify them (at least if one want to "correct" the operation that seems (according to kmymoney error window) to be incorrect. SOFTWARE/OS VERSIONS Operating System: Debian GNU/Linux 13 KDE Plasma Version: 6.5.3 KDE Frameworks Version: 6.20.0 Qt Version: 6.9.2 Kernel Version: 6.17.8+deb14-amd64 (64-bit) Graphics Platform: X11 Processors: 4 × Intel® Core™ i7-7567U CPU @ 3.50GHz Memory: 32 Gio of RAM (31.2 Gio usable) Graphics Processor: Intel® Iris® Plus Graphics 650
Created attachment 187283 [details] screenshot showing search through ledger transaction Hello, >It should be possible to have a look at the operation properties and event modify them (at least if one want to "correct" the peration that seems (according to kmymoney error window) to be incorrect. It is already possible. 1/ > have a look at the operation properties I guess you have worked with an older version (maybe 5.1.3?) of KMyMoney until recently, haven't you? until version 5.1.3, the search bar was always visible in the ledger (at the top left of the ledger). Now it still exists but you must press Ctrl+F to let it appear (see attached screenshot). The official software online documentation may not be recent enough to explain this. 2/ >and event modify them go into the ledger, scroll or search until the transaction you want to edit and DOUBLE-click on it. This is how you come to the transaction editor. In older version (<= v5.1.3), the transaction editor was always visible at the bottom of the ledger. Now it is different. A setting option allows to hide/unhide the transaction details at the bottom part of the ledger BUT this is only read-only data. Starting from v5.2.0, the only possible way of editing a transaction is a double-click on it. In my opinion, this is an improvement for developers (because only 1 data modification access instead of two to maintain) and for users because you don't have to "jump with your eyes" between a selected transaction in the middle of the screen and the its edition at the bottom of the screen anymore.
(In reply to surcouf from comment #1) > Hello, Hello ! > >It should be possible to have a look at the operation properties and event modify them (at least if one want to "correct" the peration that seems (according to kmymoney error window) to be incorrect. > It is already possible. > > 1/ > > have a look at the operation properties > I guess you have worked with an older version (maybe 5.1.3?) of KMyMoney > until recently, haven't you? Almost every version since 2006... And indeed, the last one in debian testing until now was 5.1.3. Before 2006, I had been developing my own personal finance manager ;) > until version 5.1.3, the search bar was always visible in the ledger (at the > top left of the ledger). > Now it still exists but you must press Ctrl+F to let it appear (see attached > screenshot). The official software online documentation may not be recent > enough to explain this. So it's really a search bar... It can't find the date I provide.
> So it's really a search bar... It can't find the date I provide. you're right, the search bar doesn't search through the transaction's date. This has been corrected in bug https://bugs.kde.org/show_bug.cgi?id=512748, see https://invent.kde.org/office/kmymoney/-/commit/143b31187a5f5edc979e94a88c68dd81c86822e0 so I guess this bug can be set to "resolved", cannot it?
(In reply to surcouf from comment #3) > > So it's really a search bar... It can't find the date I provide. > you're right, the search bar doesn't search through the transaction's date. > This has been corrected in bug https://bugs.kde.org/show_bug.cgi?id=512748, > see > https://invent.kde.org/office/kmymoney/-/commit/ > 143b31187a5f5edc979e94a88c68dd81c86822e0 > > so I guess this bug can be set to "resolved", cannot it? Yep.
*** This bug has been marked as a duplicate of bug 512748 ***