Bug 510312

Created attachment 185559 [details]
Correct display

I have the same problem, the selected ledger row is unreadable.
Version 5.2.1-4b18ddd (Windows 11 24H2)

Very strange. The only relevant code change between

Version 5.2.1-14d2930 (5.2-4845) - Broken
Version 5.2.1-0683f36 (5.2-4820) - OK

is https://invent.kde.org/office/kmymoney/-/commit/a31e15fc and I don't see how this could influence the foreground and/or background color.  Plus, it only happens on Windows. I can't duplicate it here on Linux using Qt5 nor Qt6.

The newer build uses a different Craft cache (which means that something basic changed). Could be the update to Qt 6.9.2.

I doubt that: The build kmymoney-5.2-4867-windows-cl-msvc2022-x86_64.exe works just fine on Win10. To me this seems another problem introduced by/on Win11.

Thomas: Which style does KMyMoney use on Windows? Breeze?

Lawrence: Does the problem also occur if you start KMyMoney from cmd.exe with `kmymoney -style fusion` or `kmymoney -style windows`?

Hi Ingo,

Launching from cmd.exe

kmymoney = has issue
kmymoney -style fusion = works correctly
kmymoney -style windows = works correctly

Hope that helps!

Lawrence.

(In reply to Ingo Klöcker from comment #6)
> Thomas: Which style does KMyMoney use on Windows? Breeze?
If KStyleManager is not available it uses breeze. See

https://invent.kde.org/office/kmymoney/-/blob/master/kmymoney/main.cpp?ref_type=heads#L108-L120

So it could be a regression in Breeze? I assume KMyMoney uses a pretty basic (when it comes to row rendering) QTreeView with alternating row colors.

*** Bug 510725 has been marked as a duplicate of this bug. ***

Is it useful that the info in https://discuss.kde.org/t/5-2-for-w11-dark-light-workaround/38247 seems to help several users?

(In reply to Ingo Klöcker from comment #9)
> So it could be a regression in Breeze? I assume KMyMoney uses a pretty basic
> (when it comes to row rendering) QTreeView with alternating row colors.

In fact it is a QTableView with a specific delegate. I have to check if there is anything special going on with colors, but I don't think so AFAIR.

*** Bug 511846 has been marked as a duplicate of this bug. ***

*** Bug 512095 has been marked as a duplicate of this bug. ***

From bug 512095 - I think it is new information that the problem appears on Win11 but not on Win10.  Hopefully this can help with troubleshooting the actual cause.

OBSERVED RESULT
In Windows 11 the selected ledger line values will now all be displayed as blank. The entry values are not deleted. If you select a different ledger entry line the original ledger line values will re-appear and the newly selected ledger line values will be displayed as blank.

EXPECTED RESULT
In Windows 10 the selected ledger line values will be highlighted in blue, and all the values readable.

SOFTWARE/OS VERSIONS
Windows 11

ADDITIONAL INFORMATION
The issue may be related to "blue highlighting" behaviour in kmymoney in Windows 11. In Windows 11 something odd is also happening in the ledger new entry form, where nearly all fields you enter data in are “highlight blue”. In Windows 10 these fields are "white".

Git commit d9fda54779320e7c1cd84eedf9f4bcdeabd5f052 by Thomas Baumgart.
Committed on 15/11/2025 at 09:05.
Pushed by tbaumgart into branch 'master'.

Change method to paint selected ledger items

Try to resolve issue with windows11 style

M  +2    -2    kmymoney/views/journaldelegate.cpp

https://invent.kde.org/office/kmymoney/-/commit/d9fda54779320e7c1cd84eedf9f4bcdeabd5f052

I appreciate that bug 512095 has been marked as resolved as a duplicate of this bug. However, I do now have a workaround that works for me in Windows 11 that does not affect anything else on the machine. As I know it is a workaround for the issues I reported in bug 512095, I felt more confident in reporting the workaround there first. However, I thought might also be useful in reporting it here it case it helps anyone else.

It is a very simple, one might say blinding obvious, workaround that I could have tried before reporting bug 512095.

The workaround that worked for me, without affecting anything else on the Windows 11 machine, was to to run kmymoney 5.2.1 in “Compatibility” mode. Windows 11 does not have a “Windows 10” “Compatibility mode, but it does have “Windows 7” and “Windows 8” compatibility modes. Both the “Windows 7” and “Windows 8” compatibility solved the issues I was observing.
I applied these compatibility modes on the kmymoney Windows “start menu” shortcut.

One other setting had to be altered to enable this. By default in Windows 11 the “Start in:” location on the kmymoney shortcut was {workingDirectory}. I am guessing this syntax is Windows 11 specific, as it is apparently not valid in compatibility mode. I changed the “Start in:” location to the kmymoney installation location.

I have not extensively using the program with this workaround in place to know if there are any other unwanted side effects.
I also attached a pdf with screenshots showing exactly what I did to bug 512095, in case there is any confusion.

*** Bug 512123 has been marked as a duplicate of this bug. ***

Git commit 16fae797fe35bcf3536924956d63a05f7e225ddb by Thomas Baumgart.
Committed on 18/11/2025 at 08:31.
Pushed by tbaumgart into branch '5.2'.

Change method to paint selected ledger items

Resolve issue with windows11 style
FIXED-IN: 5.2.2

(cherry picked from commit d9fda54779320e7c1cd84eedf9f4bcdeabd5f052)
(cherry picked from commit ba41bc3a094cd3e5a2b2fa86274a5a5b2a4c32d4)

M  +2    -2    kmymoney/views/journaldelegate.cpp
M  +1    -0    kmymoney/views/splitdelegate.cpp

https://invent.kde.org/office/kmymoney/-/commit/16fae797fe35bcf3536924956d63a05f7e225ddb

(In reply to Thomas Baumgart from comment #19)
> Git commit 16fae797fe35bcf3536924956d63a05f7e225ddb by Thomas Baumgart.
> Committed on 18/11/2025 at 08:31.
> Pushed by tbaumgart into branch '5.2'.
> 
> Change method to paint selected ledger items
> 
> Resolve issue with windows11 style
> FIXED-IN: 5.2.2
> 
> (cherry picked from commit d9fda54779320e7c1cd84eedf9f4bcdeabd5f052)
> (cherry picked from commit ba41bc3a094cd3e5a2b2fa86274a5a5b2a4c32d4)
> 
> M  +2    -2    kmymoney/views/journaldelegate.cpp
> M  +1    -0    kmymoney/views/splitdelegate.cpp
> 
> https://invent.kde.org/office/kmymoney/-/commit/
> 16fae797fe35bcf3536924956d63a05f7e225ddb

Thomas,

Thank-you for the commit. Make I ask a point of clarification please?
I am the original reporter of bug 512095, which was marked as a duplicate of this bug. In my report under "ADDITIONAL INFORMATION" I noted:

The issue may be related to "blue highlighting" behaviour in kmymoney in Windows 11. In Windows 11 something odd is also happening in the ledger new entry form, where nearly all fields you enter data in are “highlight blue”. In Windows 10 these fields are "white".

Does your commit also address what I thought might be a related issue with "highlight blue" in the ledger new entry form? This makes entering text quite difficult. I attached a PDF showing a screenshot of this potentially related issue in bug 512095. For me the workaround in Windows 11 for both issues was to use either of the “Windows 7” or “Windows 8” compatibility modes.

In 5.2.2 white-on-white in the ledger appears fixed as does the blue edit panel. Thanks.

Selected items in the List menu are still white on white.

> Selected items in the List menu are still white on white.
Yes, that's an issue of the KPageView widget provided by KDE Frameworks which is simply used by KMyMoney.