https://bugs.kde.org/show_bug.cgi?id=274130
--- Comment #22 from Simone Iori <[email protected]> --- Following up on comment #21, I looked into what a Category column would take. The value is already there: JournalModel::counterAccount(), exposed as TransactionCounterAccountRole, is what the Detail column shows today. So the column would be the same kind of change as the memo one, and "Category" already exists as a sort field. The proposal, and the points I would like your opinion on: 1. Split transactions (comment #20): reuse the role unchanged, so the column shows what the ledger already shows for a split - the counter accounts separated by commas - instead of inventing something new for it. 2. The Detail column would stop repeating the category, the way it stopped repeating payee and memo once those had their own columns. With payee, category and memo all in their own columns, Detail would be free to show the tags, which today are invisible unless "show all register entries in full detail" or the ledger lens is on. 3. Detail is also the column that stretches to fill the ledger. When the memo column is shown, that is usually the one that needs the room, so I would let the stretch follow it - the split editor already works this way, its register stretches the memo column. This is independent of the category column and touches the code of MR !396, so I would do it separately once that one is settled. -- You are receiving this mail because: You are watching all bug changes.
