Bug 435711 - Fuzzy text merged output (Hi-DPI display)
Summary: Fuzzy text merged output (Hi-DPI display)
Status: RESOLVED DUPLICATE of bug 447900
Alias: None
Product: kdiff3
Classification: Applications
Component: application (show other bugs)
Version: 1.8.5
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: michael
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-04-14 02:27 UTC by vlovich
Modified: 2023-02-12 19:17 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
Screenshot showing just the merged output is blurry/fuzzy. (81.50 KB, image/png)
2021-04-14 02:27 UTC, vlovich
Details

Note You need to log in before you can comment on or make changes to this bug.
Description vlovich 2021-04-14 02:27:50 UTC
Created attachment 137575 [details]
Screenshot showing just the merged output is blurry/fuzzy.

SUMMARY
In case this impacts anything, I have 2 4k Hi-DPI monitors connected to my laptop through a TB3 dock (the laptop monitor itself is also 4k Hi-DPI). The merge output window has blurry text whereas A/B/C windows are crisp. This applies in 2-way & 3-way diffs.

STEPS TO REPRODUCE
1. kdiff3 -m 1.txt 2.txt 3.txt

OBSERVED RESULT
Merged output is blurry. Additionally spaces are represented as dots (not sure if the latter is intended - I had thought so but I also haven't found any config option to turn it off).

EXPECTED RESULT
Text in merged output is as crisp as it is in the original content views.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Kernel 5.10.28-1LTS
(available in About System)
KDE Plasma Version: 5.21.4
KDE Frameworks Version:  5.80.0
Qt Version: 5.15.2

ADDITIONAL INFORMATION
GPU: Intel CometLake UHD Graphics & Quadro T2000. Both Intel & Nvidia (under Prime) exhibit this issue.
Display global scale: 200%
Monitors: 2 external 27" @ 3840x2160, laptop @ 3840 x 2400.

PLASMA_USE_QT_SCALING=1 doesn't impact anything.
Comment 1 michael 2023-01-22 18:31:55 UTC
Does this still happen WITH QT_ENABLE_HIGHDPI_SCALING set 1 if not I know what's going on.
Comment 2 michael 2023-01-26 21:25:35 UTC
J
Comment 3 michael 2023-02-12 19:17:25 UTC
*** This bug has been marked as a duplicate of bug 447900 ***