Progress® Telerik® Fiddler™ Classic Feedback Portal
Back to Feed
Request a Feature Report a Bug
Completed
Last Updated: 25 Mar 2018 05:00 by Imported User
Imported User
Created on: 15 Mar 2018 04:59
Type: Feature Request
28
4k font scaling not working on Windows 10
I'm using v5.0.20181.13826 for .NET 4.6.1.  I just upgraded today.  I have a 4k display running at 3840 x 2160.  I have the font scaling set to 200%.  The previous version of Fiddler worked with these settings.  I accepted the update when prompted today, but the Fiddler UI is no longer scaling the font.  Many of the menus are inaccessible or unusable.

I set my resolution to 1920 x 1080 with no scaling and the Fiddler UI was accessible.  I was able to access the menus and set the Fiddler font to 16, and returned to my regular 4k display settings.  Most of Fiddler was readable under this setting, but several areas don't appear to acknowledge this change.  Screen shots attached.
27 comments
Imported User
Posted on: 25 Mar 2018 05:00 
Latest update worked a treat for me! Thanks!
Tyson
Posted on: 20 Mar 2018 05:00 
Just got the latest update (v5.0.20181.14850). The UI is better but is still a bit blurry when viewed at 150% on my 4K.
Imported User
Posted on: 18 Mar 2018 05:00 
Open the Fiddler.exe Properties window, switch to the compatibility panel and find system enhanced DPI zoom to resolve
Imported User
Posted on: 18 Mar 2018 05:00 
I want to go back to previous version. How do I do that? This is terrible.
Imported User
Posted on: 16 Mar 2018 05:00 
A few more interesting observations.

The current and previous release both have the same behavior when using -dpiaware flag. I'm seeing that with a larger font set under appearance, text gets clipped inside the elements - looks ugly but works. The previous version v5.0.20173.50948 handles text size changes without the -dpiaware flag much better.

My primary monitor is at 2560x1440. Secondary (laptop screen) is at 1920x1080. DPI at 125%

v5.0.20173.50948 for .NET 4.6.1
Built: Thursday, December 14, 2017

64-bit AMD64, VM: 43.0mb, WS: 85.0mb
.NET 4.6.2 WinNT 10.0.16299.0
Imported User
Posted on: 16 Mar 2018 05:00 
I installed the below version and no issues.

v5.0.20173.50948 for .NET 4.6.1
Built: Thursday, December 14, 2017

64-bit AMD64, VM: 46.0mb, WS: 92.0mb
.NET 4.6.2 WinNT 10.0.16299.0

DPI setting to 125% in Windows

I let it auto update to v5.0.20181.13826 and the issue immediately came back.

Using the -dpiaware flag fixed it!
Imported User
Posted on: 16 Mar 2018 05:00 
I rolled back to my previously installed version of v4.6.20173.38786 and the issues does not present itself.
Imported User
Posted on: 16 Mar 2018 05:00 
Installing v5.0.20173.50948 fixes the issue for me without having to do anything with -dpiAware. -dpiAware did improve the latest version, but there were still slight issues where tabs seemed too short in height.

1. Resolution 2880 x 1800, scaling = 200%
2. No
3. 10.1709.16299.309
4. .NET Framework 4.7.1
5. Yes. 5.0.20173.50948
Imported User
Posted on: 16 Mar 2018 05:00 
I rolled back to my previously installed version of v4.6.20173.38786 and the issues does not present itself.
Tsviatko
Posted on: 16 Mar 2018 05:00 
We are not able to reproduce the problem to its full extent locally. So, it would be really nice if you guys could help us a bit further. Here are the six previous public versions of Fiddler. (https://telerik-fiddler.s3.amazonaws.com/fiddler/FiddlerPreviousVersions/FiddlerPreviousVersions.zip) What would help us is:

1. What is the resolution of the monitor where Fiddler exhibits this problem?
2. Are there other monitors on the system? What are their resolutions?
3. What is the full Windows version?
4. What is the most recent .NET version installed?
5. Does any of the previous Fiddler versions behave differently? Which one?
Tsviatko
Posted on: 16 Mar 2018 05:00 
And least but not least

6. Are you running Fiddler with the -dpiaware parameter or not?
Imported User
Posted on: 15 Mar 2018 05:00 
Re: Tsviatko Yovtchev: just updated today. Not sure what previous version I was using, but I have autoupdates enabled and I was using fiddler earlier this week without having been prompted for an update. I assume the previous version worked.
Imported User
Posted on: 15 Mar 2018 05:00 
The GUI is now unuseable on a high res display. using a Surface Tablet with default settings.
Imported User
Posted on: 15 Mar 2018 05:00 
The problems relies in the high-dpi awareness of Fiddler.

A temporary workaround is to suppress Fiddler high-dpi management going into the Fiddler.exe file properties:

* Compatibility Tab
* Check the option: "Override high DPI scaling behavior"
* in the combo box specify: "System"

In any case something has definitely changed in Fiddler or Windows since it never happened before.
The test must be done with high-dpi monitors and specifying a magnification > 100% (e.g. 150%)

HTH
YYX
Posted on: 15 Mar 2018 05:00 
I'm seeing the exact same issue. Hope be fixed asap.
Tsviatko
Posted on: 15 Mar 2018 05:00 
What version did you guys update from? We haven't really changed anything UI related in the new release. It has to be some change in Windows I guess. I could provide an old version of Fiddler to test that theory. I just have to know which one.
Imported User
Posted on: 15 Mar 2018 05:00 
The GUI is now unuseable on a high res display. using a Surface Tablet with default settings.
Imported User
Posted on: 15 Mar 2018 05:00 
The problems relies in the high-dpi awareness of Fiddler.

A temporary workaround is to suppress Fiddler high-dpi management going into the Fiddler.exe file properties:

* Compatibility Tab
* Check the option: "Override high DPI scaling behavior"
* in the combo box specify: "System"

In any case something has definitely changed in Fiddler or Windows since it never happened before.
The test must be done with high-dpi monitors and specifying a magnification > 100% (e.g. 150%)

HTH
Imported User
Posted on: 15 Mar 2018 05:00 
The GUI is now unuseable on a high res display. using a Surface Tablet with default settings.
Imported User
Posted on: 15 Mar 2018 05:00 
The problems relies in the high-dpi awareness of Fiddler.

A temporary workaround is to suppress Fiddler high-dpi management going into the Fiddler.exe file properties:

* Compatibility Tab
* Check the option: "Override high DPI scaling behavior"
* in the combo box specify: "System"

In any case something has definitely changed in Fiddler or Windows since it never happened before.
The test must be done with high-dpi monitors and specifying a magnification > 100% (e.g. 150%)

HTH
Imported User
Posted on: 15 Mar 2018 05:00 
The GUI is now unuseable on a high res display. using a Surface Tablet with default settings.
Imported User
Posted on: 15 Mar 2018 05:00 
The problems relies in the high-dpi awareness of Fiddler.

A temporary workaround is to suppress Fiddler high-dpi management going into the Fiddler.exe file properties:

* Compatibility Tab
* Check the option: "Override high DPI scaling behavior"
* in the combo box specify: "System"

In any case something has definitely changed in Fiddler or Windows since it never happened before.
The test must be done with high-dpi monitors and specifying a magnification > 100% (e.g. 150%)

HTH
Imported User
Posted on: 15 Mar 2018 05:00 
The GUI is now unuseable on a high res display. using a Surface Tablet with default settings.
Imported User
Posted on: 15 Mar 2018 05:00 
The problems relies in the high-dpi awareness of Fiddler.

A temporary workaround is to suppress Fiddler high-dpi management going into the Fiddler.exe file properties:

* Compatibility Tab
* Check the option: "Override high DPI scaling behavior"
* in the combo box specify: "System"

In any case something has definitely changed in Fiddler or Windows since it never happened before.
The test must be done with high-dpi monitors and specifying a magnification > 100% (e.g. 150%)

HTH
Imported User
Posted on: 15 Mar 2018 05:00 
The GUI is now unuseable on a high res display. using a Surface Tablet with default settings.
Imported User
Posted on: 15 Mar 2018 05:00 
The problems relies in the high-dpi awareness of Fiddler.

A temporary workaround is to suppress Fiddler high-dpi management going into the Fiddler.exe file properties:

* Compatibility Tab
* Check the option: "Override high DPI scaling behavior"
* in the combo box specify: "System"

In any case something has definitely changed in Fiddler or Windows since it never happened before.
The test must be done with high-dpi monitors and specifying a magnification > 100% (e.g. 150%)

HTH
Imported User
Posted on: 15 Mar 2018 05:00 
I'm seeing the exact same issue. I then added the -dpiAware switch to the shortcut which helped some but parts of the app are still displaying wonky. See screenshot.
Create an account Log In
View
Type
Status