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

--- Comment #4 from pc <[email protected]> ---
Thomas,

I have a bit more information on this issue, and have now been able to
reproduce this issue on a Windows system that was not previously showing the
issue.

The two Windows 10 machines I saw the issue on are quite old devices, with a
lower "native" screen resolution that all recent devices. These "native" screen
resolutions are:
1680x1050
1366x768

I also have access to a Windows 11 devices with a more standard "native" screen
resolution of 1920x1080. On this machine there was no "Home Tab Reconciled Date
Field" text wrapping. So I carried out a few experiments changing the screen
resolution of this device, and with some resolutions the date wrapping
occurred.

Resolution    Home Tab Reconciled Date Field
1920x1080    No wrapping
1680x1050    No wrapping
1440x900      Wrapped
1366x768      Wrapped
1280x720      Wrapped

Note that no wrapping occurred at 1680x1050, as had occurred on my Windows 10
machine. Though for the Windows 10 machine 1680x1050 is the "native" display
resolution, whereas for the Windows 11 machine 1920x1080 is the "native"
display resolution..

I also tried the same experiment on a Linux machine (Ubuntu 2024.04.3) with a
"native" screen resolution of 1920x1080. This did not show the issue. The dates
are displayed as expecting, with no wrapping, for all the display resolutions
listed above.

I am guessing that at some point in the code the required width of the "Home
Tab Reconciled Date Field" text boxes has to be calculated as a number of
display pixels. So I am wondering if for some display resolutions in Windows
whether there is something like a rounding down, rather than rounding up,
occurring in the calculation, which may show as an issue on lower resolution
displays?

I used the "KMyMoney test data file" test file I previously attached to this
ticket, and KMyMoney 5.2.1-6e26843 (build 5181) for these experiments.

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

Reply via email to