This forum has been archived. All content is frozen. Please use KDE Discuss instead.

Split transactions/VAT: How to show actual Category

Tags: None
(comma "," separated)
crun
Registered Member
Posts
10
Karma
1
When using VAT split, the second line of the ledger entry changes from showing the category (e.g" Vehicle:fuel")
to just showing "split transaction"
This is both on the ledger second line, and in the ledger detail edit fields below.

Since (almost) everything has VAT, this is completely useless, as now I can't see what category it is until I edit right into the split dialog.

Is they any way around this?

What I would like is to see:
"Vehicle:fuel , GST Paid"
("GST Paid" is the VAT category)
User avatar
ipwizard
KDE Developer
Posts
1359
Karma
6
OS
As mentioned in another thread, hovering over the text in the ledger shows a tool tip with the details, but your suggestion is also a possibility to solve the issue. I opened a wishlist item for it, so that we don't forget.


ipwizard, proud to be a member of the KMyMoney forum since its beginning. :-D
openSuSE Leap 15.4 64bit, KF5
crun
Registered Member
Posts
10
Karma
1
ipwizard wrote:As mentioned in another thread, hovering over the text in the ledger shows a tool tip with the details

Thanks that helps a lot.
(but it would still be much nicer to just see category and split)
User avatar
ipwizard
KDE Developer
Posts
1359
Karma
6
OS
A future version of KMyMoney will display the list of categories instead of the text "Split transaction".


ipwizard, proud to be a member of the KMyMoney forum since its beginning. :-D
openSuSE Leap 15.4 64bit, KF5
crun
Registered Member
Posts
10
Karma
1
Looking forward to it.

BTW, I personally like to see the build date in the about box.
Since current versions are built daily, and have an obscure version hash instead of a sequential number (Version 5.0.8-d8052a6) , it doesn't leave you with much idea how old it is.
User avatar
ipwizard
KDE Developer
Posts
1359
Karma
6
OS
The version hash is only obscure to the normal user, it is not to the developers, as it identifies exactly the source code state used to create the version the user is running. A date is ambiguous because one can create an executable based on any source code state on a given date. Looking at that date does not give a developer a clue which code base was used to create it. We could try to add the build date as well, but I doubt that the git sha1 hash (that obscure piece) will be replaced.


ipwizard, proud to be a member of the KMyMoney forum since its beginning. :-D
openSuSE Leap 15.4 64bit, KF5


Bookmarks



Who is online

Registered users: Bing [Bot], Evergrowing, Google [Bot]