https://bugs.kde.org/show_bug.cgi?id=516469

--- Comment #11 from Laura <[email protected]> ---
Thank you for your reply.  I have done as both of you suggested increasing the
columns in the header and widened.  That fixed that issue.  Thank you

For split transactions, I go through the steps outlined in the video provided
earlier.  New transaction, amount, arrowdown select category, split icon, split
screen pops up, double click to edit, change the amount for the category
selected, enter.  New, go through same process, everything totals correctly,
then I click ok, the program closes.  The transaction is not recorded.  I hope
this makes sense.

I am on KMYMoney version 5.2.1-eda3fb1

I am running the program on Windows 11.

I hope this additional information helps.

Sincerely,

Laura Williams

----- Original Message -----
From: "Thomas Baumgart" <[email protected]>
To: "laurawlms tds. net" <[email protected]>
Sent: Saturday, February 28, 2026 8:46:08 AM
Subject: [kmymoney] [Bug 516469] Subcategory and split transactions

https://bugs.kde.org/show_bug.cgi?id=516469

--- Comment #10 from Thomas Baumgart <[email protected]> ---
Paul is right about the width of the column. It's just a bit too narrow. Move
the mouse over the little bar between the columns in the header. Once there,
the mouse cursor shape should change. Then double click on this  spot and the
column should widen as much as necessary for the data in the column. Another
method is to drag that other shape to the right which will also widen the
column.

Regarding the split transaction I am not sure what you are referring to. Maybe,
you can describe which buttons you press and which data items you fill before
the crash happens (KMyMoney shuts down).

And just for reference: which operating system are you using KMyMoney on and
which version of KMyMoney do you use (see Help/About KMyMoney). Mine currently
shows "Version 5.2.70-f8e3a10bd". Don't worry if yours is different, we just
need to know what it is.

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to