Repository navigation
IDLE: Tiny font on HiDPI display #75681
Description
Activity
My new laptop has a HiDPI display (3840x2160). IDLE (as well as other Tk applications) looks ugly on it. The font of menu and dialogs is tiny. The font used in editor and shell looks normal size. I use Linux with X Window.
It seems to me this issue doesn't have solution. Related links:
https://wiki.tcl.tk/41949
https://core.tcl.tk/tk/tktview/0917069c05e9c354a27c8105a7a22264090b9274
https://stackoverflow.com/questions/34132203/scaling-of-tkinter-gui-in-4k-38402160-resolutionPR 3639 adapts the receipt from [1]. I'm not sure that it doesn't add regressions on low-DPI displays.
The TkFixedFont initially used in Shell and editor has its size set to 10 if initially negative. Users can only replace this with a real font, not another of tk's abstract fonts.
On windows, the sizes of the nearly 20 fonts touched by the patch range from 8 to 12. So no possible regression there. If the sizes on Linux were in the range -8 to -12, then the effect is to replace the size with numbers around 10 instead of exactly 10 (as IDLE currently does). But from what you said on the patch, the negative numbers are not exactly the negative of their real size, but are tuned for positioning.
Cheryy, Louie, and Ned: the patch needs to be test on multiple *nix machines, especially on OSX, to make sure it does not mess up on standard monitors. A quick 'git pr 3639' and 'python -m test.test_idle' would be helpful.
Tests run on Ubuntu. The menubar is bigger now though, so it's default is
different than before. Maybe that was the only way to fix it, but it's now
about twice as big as the shell font.Attached screen prints of configdialog. It's messed up.
Thank you Cheryl. That is enough to reject the patch is it is now.
The negative sizes are pixels. I think it might be better to multiply them by a systems specific factor, but only when needed.
One might wish that the scaling should be handled automatically, in tkinter if not in tk itself. But it was mentioned in one of the links that displays do not always report their dpi correctly.
One possibility is a tkinter calibration app that displays a 500 or 1000 pixel line (user selects) and asks the user to input the physical length (centimeters or inches). (Some games do something similar with brightness.)
To check whether a tkinter scaling app could be used, I sized Serhiy's image so that the sample font in the Settings Font tab matched the sample font in a real box. The system font around it is tiny but readable, especially with a magnifier.
This is a tkinter issue, not only an IDLE issue, but IDLE is a good test app, with realistically complex dialogs. Lacking a Python-wide fix, something could be added to the Font tab -- for instance a dpi multiplier that defaults to one. It would only be used if not 1.0.
I reread config.IdleConf.GetFont. Rather than manipulate one of tk's default fonts ('TkFixedFont'), it creates a normal font sized in points. It uses 'TkFixedFont' as a handy key for finding a system-specific sure-to-exist fixed pitch font: "actualFont = Font.actual(f)", where f is a TkFixedFont instance. Thus it does not affect the dialogs.
It would be helpful to know if HiDPI screens on Windows have a problem.
bpo-31496 is about test_configdialog failing on the same HiDPI screen.
The Keys and General tabs are messed up even more on my computer. Some sections are just not visible. This is because The dialog window uses hardcoded size in pixels, it is too small for all content. After removing the hardcoded size all looks good.
Cheryl, what do you get with
import tkinter as tk root = tk.Tk() print(float(root.tk.call('tk', 'scaling')))
If it is less than 1.2, then Serhiy's revised patch should leave config dialog as it should be.
>>> import tkinter as tk >>> root = tk.Tk() >>> print(float(root.tk.call('tk', 'scaling'))) 1.3333333333333333
11 remaining items
What about 2.7?
I take it you want this reopened. I have not touched IDLE 2.7 for over a year, but since a) there have been no complaints about the patch in released 3.6.3/4, b) we recommend the same tk 8.5.18 for both 2.7 and 3.6, and c) this is a crippling regression upon equipment upgrade, I will review and manually test on Windows a combined backport of both PRs first tested on a Linux or Mac system. It should be tested on a HiDPI system before a merge.
I guess I was not clear enough that I will test on Windows after someone else does a backport that works on Linux.
You promised to make backports to 2.7 when did the mass files renaming. The simple cherry-picking doesn't work, and I even don't know what files in 2.7 should be changed.
Something was changed on my computer (I upgraded the OS twice since creating this issue), and now I don't see any difference between patched and unpatched 2.7. Terry, could you please test whether there are any visible effects on Windows?
Does IDLE now work on your HiDPI screen without the patch? or does it not work even with the patch?
I just got a 2.7 worktree working with Python built. 2.7.15+ comes with 8.5.19 instead of 8.5.15. IDLE runs as I expect and windows look normal, as with 3.x, both before and after the patch.
If calling fix_scaling ever causes anyone a problem on some particular combination of OS, Python, and Tk versions, they could neutralize it by adding the following after the current definition.
def fix_scaling: pass
Seems IDLE now works on my HiDPI screen without the patch. It looks the same as IDLE in 3.x with the patch.
My inclination, then, is to close this issue and PR until there is a demonstrated need for change and a test machine to verify the fix for 2.7 and 8.5.19.
Just tested on a 13" Retina MacBook Pro (2560x1600), everything looks fine.
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields: