New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Implement per-monitor High-DPI support on Windows #96

Open
nesteruk opened this Issue Sep 18, 2016 · 4 comments

Comments

Projects
None yet
3 participants
@nesteruk
Copy link

nesteruk commented Sep 18, 2016

I have a 4K laptop screen. The editor window and menus are ok, but all of the toolbars look terrible. Would be nice if high-DPI supporting code was added so that UI elements are scaled to OS settings. Thanks!

@otfried

This comment has been minimized.

Copy link
Owner

otfried commented Sep 18, 2016

In prefs.lua, set

prefs.ui_scale = 200
prefs.toolbar_scale = 200

@otfried otfried closed this Sep 18, 2016

@otfried otfried added the enhancement label Sep 24, 2016

@otfried otfried changed the title High-DPI support Implement per-monitor High-DPI support on Windows Sep 24, 2016

@otfried otfried reopened this Sep 24, 2016

@otfried otfried self-assigned this Oct 5, 2016

@alanrunner

This comment has been minimized.

Copy link

alanrunner commented Jul 30, 2018

I also have a 4K monitor. I made the suggested changes to these setting in prefs.lua in version 7.2.7, and they had no effect. The icons on the toolbar were the same size after restarting IPE and are still too small for me to see clearly.

@otfried

This comment has been minimized.

Copy link
Owner

otfried commented Jul 30, 2018

How are you modifying the settings? Editing the prefs.lua file in the Ipe distribution directly?

In 7.2.7, Ipe will actually pick up the DPI from the system if the settings are left at 100, but not on a per-monitor basis. What is the resolution setting in your Windows control panel?

@alanrunner

This comment has been minimized.

Copy link

alanrunner commented Jul 30, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment