This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author aroberge
Recipients aroberge, cheryl.sabella, serhiy.storchaka, taleinat, terry.reedy
Date 2019-05-26.01:05:53
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CAGMu_=qX-UzMj95mVDYxo5ZxPTndsGyKpqDaY5X7hHYB07t-xw@mail.gmail.com>
In-reply-to <d2607744-488e-0993-98f5-3fabeeaae16d@udel.edu>
Content
On Sat, May 25, 2019 at 9:49 PM Terry J. Reedy <report@bugs.python.org>
wrote:

>
> Terry J. Reedy <tjreedy@udel.edu> added the comment:
>
> Thank you.  Along with your path browser report, things are much
> clearer.  With variable pixel densities and custom settings, we cannot
> use fixed pixel or even mm numbers. 114 is right for me because I have
> Display Setting "Change the size of text, apps, and other apps, and
> other items" to 125%.

Yes, that's the settings I was talking about (my OS is in French, so I
couldn't quote you the exact text.)

Mine is set at 200%, as recommended by Windows -  and which makes the text
just large enough to be readable for me.

My taskbar is 11+mm high.   78 or something near
> that is right for 100%.  150% would need more than 114.
>
> Under 'Advanced scaling settings', one can enter a custom scaling size.
> Is this what you meant when you said you set scaling to 200% or 100%.
>
Yes, see above.

> No need to post what you wrote.  Let me summarize the numbers I want
> along with mine for comparison.
>
> What I need to do now is examine the tk screen sizing system and
> functions and see if the needed numbers (max usable height for zoom) are
> available.  If not, I might add a 'Calibrate screen' item under Options.
>
>
I think that would possibly work out best - people could customize to their
liking. With so many different display, including 4k monitors, it makes
sense to just make it user-configurable.

André

> On 5/25/2019 6:42 PM, Andre Roberge wrote:
> >
> > Andre Roberge <andre.roberge@gmail.com> added the comment:
> >
> > Thanks.
> >
> > I did a quick check. 114 solves the problem of the Restore Height not
> > working, but the status bar is still hidden.  To me, the crucial part of
> > the problem was the restore height not working, so I'd be happy with
> this.
> >
> > At 164, I can see parts of the status bar
> > [image: image.png]
> >
> > At 180, there is a tiny gap
> >
> > [image: image.png]
> >
> > 178 seems to be just touching.
> >
> > [image: image.png]
> >
> > With the vertical resolution of my screen being 2000 px, tiny gaps are
> > essentially invisible.  Because of this huge resolution, most display
> > elements (text, icons ... and the taskbar) are set up to be twice as big
> -
> > this is the 200% factor I was referring to. So, in pixel terms, the
> taskbar
> > on my computer is likely twice as high as yours.
> >
> > Using a measuring tape, the physical size of my screen is 183 mm; the
> > taskbar is 8 mm high.
> >
> > I can add these comments (and screenshots?) on the bug tracker if you'd
> > like.
> >
> > Thanks for finding the solution to this problem.
> >
> > André
> >
> > P.S. I *just* started using IDLE again as I want to use it as a basis for
> > my project.  The last time I had used IDLE was with Python 2.4 - I
> quickly
> > moved on to using other editors. There's been tremendous progress since
> and
> > I want to thank you for all your work.
> >
> > On Sat, May 25, 2019 at 7:11 PM Terry J. Reedy <report@bugs.python.org>
> > wrote:
> >
> >>
> >> Terry J. Reedy <tjreedy@udel.edu> added the comment:
> >>
> >> The current patch fixed the hidden status bar on Windows.  I just had to
> >> increase the margin reserved for the taskbar from 76 to 114.  This will
> >> also work if the taskbar is moved to the top of the screen.  If the
> taskbar
> >> is moved to either side or if it is less high for previous versions of
> >> Windows, a visible margin is better than a hidden status bar.
> >>
> >> ----------
> >>
> >> _______________________________________
> >> Python tracker <report@bugs.python.org>
> >> <https://bugs.python.org/issue37039>
> >> _______________________________________
> >>
> >
> > ----------
> > Added file: https://bugs.python.org/file48358/image.png
> > Added file: https://bugs.python.org/file48359/image.png
> > Added file: https://bugs.python.org/file48360/image.png
> >
> > _______________________________________
> > Python tracker <report@bugs.python.org>
> > <https://bugs.python.org/issue37039>
> > _______________________________________
> >
>
> ----------
>
> _______________________________________
> Python tracker <report@bugs.python.org>
> <https://bugs.python.org/issue37039>
> _______________________________________
>
History
Date User Action Args
2019-05-26 01:05:53arobergesetrecipients: + aroberge, terry.reedy, taleinat, serhiy.storchaka, cheryl.sabella
2019-05-26 01:05:53arobergelinkissue37039 messages
2019-05-26 01:05:53arobergecreate