[Octave-bug-tracker] [bug #41938] Terminal fonts do not scale properly with a display scaling of 150% and more

[Delbert Johnson]

Follow-up Comment #12, bug #41938 (project octave):

This comment is directed to answer the questions in comments 9 and 11

Comment#9.  I did decrease the screen resolution to 1920x1080 via the display
property control.  This reduced the resolutions for all applications and did
not correct the problem.

Comment#11. I thought that the Windows Compatibility Center link, in the
reference cited in my original comment(#7), would provide additional
information that would be useful for developers.  It turns out that it does
not.  A better link is:

https://msdn.microsoft.com/library/windows/desktop/dn469266.aspx

The fix is complex if you are trying to make the application work on multiple
monitors but.  If possible this problem should be fixed with the release of
version 4.  Apparently many of the old applications assumed a 95 DPI screen
resolutions.  There are now API's available to detect higher resolution
screens.  

The Editor and Documentation frames don't have the problem that is occurs in
the Command Window.  John comments in #8 that the editor(tab) in the
File-Preferences is not fixed with the solutions that I provided in comment
#7.  It did not get fixed for me neither.  However, the other tab-frames in
the File-Preferences did get fixed.  Again, the solutions might be to look at
how the General, Editor Styles and Terminal frames were written (which display
ok) compared to the Editor preference frame that does not display correctly.

I am a c, c++, c# programmer.  I'm not set up to replicated the development
environment to fix the code but I would be willing to look at the code written
for these frames that work and don't work and, if necessary research Microsoft
recommendations on Hi Resolution screens in order to recommend modifications
to the code to fix these problems.  It would be up to another programmer to
run and test the changes to see if if fixes the problem.



    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?41938>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/