Skip to content
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

Using system default settings or custom settings for fonts #78

Open
hackwrench opened this issue Apr 18, 2016 · 2 comments
Open

Using system default settings or custom settings for fonts #78

hackwrench opened this issue Apr 18, 2016 · 2 comments

Comments

@hackwrench
Copy link

I'm using a preview build of Win10
I have a TV that is hooked up to a laptop, The TV is smaller than 32" and larger than the laptop's 15", 720p. The font is not large enough for me to read easily at the distance I sit from the TV.
There are system font sizes at Control Panel\All Control Panel Items/Display It would be nice if Microsoft provided more suggestions than the items listed there, but that's another problem.

@randomascii
Copy link
Collaborator

I'm not sure what the options are for addressing this. Marking the application as high-DPI aware? Explicitly changing the font? It will be important to make sure that the dialog doesn't grow to be larger than your screen's resolution, since off-screen buttons are a bigger problem than too-small buttons.

In most cases I only ever click Start Tracing and Save Trace Buffers, so readability isn't much of a concern. I guess readability of the trace information can be important when recording information about the analysis.

@mwinterb
Copy link
Contributor

If you haven't already looked into it, UIforETW is already marked as high-DPI aware (at least, as of the last release). It explicitly needs Per Monitor High-DPI awareness.

That change is trivial, but handling of the WM_DPICHANGED still needs to happen to actually make the dialog react to the new DPI once the dialog has moved from one display to another. Which may be trivial to do, it just did not happen automatically.

It seems that the DPI selected for a pre-"monitor specific DPI-aware" application is the DPI of the main display, so a temporary workaround for @hackwrench may be to make the TV the main display, but that may have other unwanted consequences.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants