bpo-31500: IDLE: Scale default fonts on HiDPI displays.#3639
Conversation
|
Sorry, something went wrong.
|
I was about to ask, how to we avoid enlarging the fonts when they should not be enlarged, as on Cheryl's system. How did you pick 1.2? On my system, with a 27" 2560 x 1440 widescreen, which I believe is not 'HiDPI', it is 1.333. In my display settings, I selected "Enlarge fonts...: 125%". I don't know if that affect tk's reported scaling factor. How about adding On some Linux systems, the reported size of at least TkFixedFont is 0. See bpo-26673, which changed the GetFont line 'if size < 0' to '<= 0'. Do you have any such thing on your machine? What does the following show? For me: |
Sorry, something went wrong.
|
I created #3664 to immediately remove the dialog size, so I can more forward with other patches that would require it to be revised or removed. I will adjust this one once it is merged. |
Sorry, something went wrong.
|
Merge 223caaa includes the size removal. |
Sorry, something went wrong.
|
On Ubuntu: |
Sorry, something went wrong.
This is arbitrary.
On Windows all sizes are positive, isn't? They are not changed.
The same as @csabella. |
Sorry, something went wrong.
|
run.py already imports sys , so it seems somewhat sensible to avoid the useless loop on windows, but this is not critical. I will presume that the current patch works fine on your machine. I decided not to worry for now about any monitors or systems that lie about the scaling. That is a bug on someone else's part. |
Sorry, something went wrong.
|
Thanks @serhiy-storchaka for the PR 🌮🎉.. I'm working now to backport this PR to: 2.7, 3.6. |
Sorry, something went wrong.
…GH-3639) (cherry picked from commit a96c96f)
|
Thanks @serhiy-storchaka for the PR 🌮🎉.. I'm working now to backport this PR to: 2.7. |
Sorry, something went wrong.
|
Sorry, @serhiy-storchaka, I could not cleanly backport this to |
Sorry, something went wrong.
https://bugs.python.org/issue31500