Summary: | Drop down menus / listboxes mostly disappear on mouse-over and only show the item which the mouse is currently over | ||
---|---|---|---|
Product: | [Applications] kmymoney | Reporter: | Lawrence Wright <lwright> |
Component: | ux-ui | Assignee: | KMyMoney Devel Mailing List <kmymoney-devel> |
Status: | RESOLVED NOT A BUG | ||
Severity: | major | ||
Priority: | NOR | ||
Version First Reported In: | 5.2.0 | ||
Target Milestone: | --- | ||
Platform: | Microsoft Windows | ||
OS: | Microsoft Windows | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: | Example of menu breakup |
Description
Lawrence Wright
2025-07-29 18:02:04 UTC
Does the same happen with context menus (when you right click on something to get the available menu options for that type of item?) (In reply to Jack from comment #1) > Does the same happen with context menus (when you right click on something > to get the available menu options for that type of item?) Yes, I can confirm it does! Also realised I'd taken a screenshot of the menu breakup and forgot to attach it, so have done that now together with an example context menu from right clicking in the "days to forecast" box on the forecast page. Created attachment 183641 [details]
Example of menu breakup
Can you give the version as reported by Help/About KMyMoney. Thanks. (In reply to Jack from comment #4) > Can you give the version as reported by Help/About KMyMoney. Thanks. Hi Jack, no problem: Working: 5.2.0-1cf050c Broken: 5.2.0-cb50551 Broken: 5.2.0-cf01f04 Note that I haven't exhaustively tried all versions, just what I've got to hand, and the stable download available today. Thanks! I have a suspicion that the change from working to broken was when the build changed from Qt5 based to Qt6 based, and we have a few other bugs with the same history. If that's the case, we just need to track down what changed in Qt to cause this. Possibly tedious, but doable. (In reply to Jack from comment #6) > I have a suspicion that the change from working to broken was when the build > changed from Qt5 based to Qt6 based, and we have a few other bugs with the > same history. If that's the case, we just need to track down what changed > in Qt to cause this. Possibly tedious, but doable. That definitely sounds like a reasonable probability! Fingers crossed it's not too bad to track down :) I just checked 5.2.0-cf01f04 on a Windows 10 installation: no problem. How do other KDE applications (e.g. Kate) perform in this case? (In reply to Thomas Baumgart from comment #8) > I just checked 5.2.0-cf01f04 on a Windows 10 installation: no problem. How > do other KDE applications (e.g. Kate) perform in this case? Hi Thomas, Tried Kate - worked fine. Had a hunch that it might be to do with High DPI scaling as I have a 4k 14" laptop screen... turns out that on an earlier version I had to set compatibility settings for KMyMoney as follows: High DPI scaling override Override high DPI scaling behaviour. Scaling performed by: "System" Because I've upgraded all the way from 5.0, this was still set - I tried turning this setting off and restarting Version 5.2.0-cf01f04 and all is well now - presumably Qt6 improves high DPI behaviour. Thanks for your time and this can be resolved now - hopefully useful info if anyone else comes across it. Thanks for the feedback. |