-
Notifications
You must be signed in to change notification settings - Fork 6.6k
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
Enable ClearType in PT Run #4172
Comments
Cool. A screenshot for showing blurriness would be helpful too. |
@crutkas Yeah, well, Unfortunately my screen is so low res you can't even see the blurriness(in a screenshot)...so, I guess after I send a PR maybe someone with a better screen could do that 😅 |
Looks like AnuthaDev has abandoned his PR, the PR looks good apart from the multiple "Windows Versions" upgrade. |
@royvou I actually messed up my branch so I had to abandon that PR😅😅. Don't worry, working on it now :) |
No worries, good to know if it still active :) ! |
From #5920, screen resolution is 768x1366, with an 100% scaling, |
That's exactly the same as mine. I believe this PR would only significantly improve lower than FHD screens. |
Fix added in 0.21.1, please go to https://github.com/microsoft/PowerToys/releases to upgrade |
Summary of the new feature/enhancement
After the migration from XAML islands to WPF, text rendering of PT Run on my 1366x768 display is unbearable. My eyes hurt looking at the text. This is because ClearType is not enabled.
Proposed technical implementation details (optional)
After some fiddling around with code, this is what needs to be done:
Modify DropShadow in MainWindow.xaml
Enable ClearType in TextBox
Enable Overall ClearType by setting RenderOptions.ClearTypeHint to Enabled and TextOptions.TextFormatting to Display in MainWindow.xaml
After applying the above patches, PT Run text rendering is fantastic on my screen. But we would need to make sure it does not cause regressions in high res displays (which I don't have😅)
@crutkas I would like to work on it :)
The text was updated successfully, but these errors were encountered: