I guess there still is no point in ordering a 4K display.

I guess there still is no point in ordering a 4K display.

Still blurry in 10.1 Berlin.

Seriously, EMBT?


32 thoughts on “I guess there still is no point in ordering a 4K display.

  1. I use a macbookpro retina as dev machine , i must admit that it has impacted my developments since a year and a half in a very negative way. Blurry text = unusable. It is not meant as a criticism but as an observation.

  2. I’d say its the font. Try Segoe UI Size 9 on your forms, then your app is also blurry. Makes me headache. I switched to segoe since 10S and it was ok on 3k.

    But i’ve no idea if you can change the font for the IDE.

  3. You need a 4K display before you clients users get it. Especially if you deliver VCL (Win32) applications (imho). I have told admins for 0.5K users windows 10 is ok, but refrain from 4k displays for another year 🙂 [Or pay me by the hour to workaround].

  4. And Win10 itself has some stuff that does do it at all. The desktop (!) needs an login-logout after scale change. Any user setting a scale non-dividable by 100 (ah, nomenclature, i mean multiples of 100) will see crappy stuff in a lot of applications. Chrome is one widely used. 

  5. As I am visual impaired I cannot appreciate the benefits of a 4k display. Currently I’m running at 1680 x 1050 and feels like fonts are too small. Maybe that 4K display are not best suited for developing, but instead more useful for image editing?

  6. Fabio VITALE What about your cellphone/tablet? Do you even notice that it scales to a very high resolution? You feel the fonts are too small on 1680×1050. Now imagine how would your fonts look like in the size of 0.2″ on 1680×1050 and on 4K. Which one would you look at the whole day?

    Lars Fosdal Is that something you would run and test? http://windows10_dpi_blurry_fix.xpexplorer dot com , or did you find something?

  7. I still don’t see the point of 4K if scaling is used. Why buy lots of pixel real estate and put it to waste by scaling it? If you can’t see stuff at 100% then you don’t need it. That’s just my sad opinion though. I know display manufacturers will say differently.

  8. Lars Fosdal You mention that your VCL app is blurry. I want to show everyone that it is possible to make a crisp non-blurry VCL app.

    Here is a picture of a VCL app that shows the two “Enable High-DPI” settings side by side.

    You can see the one on the left is the “normal” blurry version. The one on the right is has “Enable High-DPI” checked.


    Make sure you download and open it up to full size.

    Retina screen Windows 10 with 200% scaling.

  9. 200% is not a problem, 125%, 150%, 175% is.

    I.e. when the system needs to do pixel rounding. I’m not sure what the difference is between the VCL which appears blurry and the other apps that don’t.

  10. Lars Fosdal”200% is not a problem, 125%, 150%, 175% is. I.e. when the system needs to do pixel rounding. ”

    I haven’t tried at those percent yet because this is what my monitor is set for. I will do it sometime.

    But I don’t think it has anything to do with “pixel rounding”. In Windows High-DPI text is drawn the normal way, namely, with vector drawing of TrueType fonts. There are no pixels involved. So it shouldn’t matter what the percentage is. The only time pixels are involved is when the app is NOT DPI aware.

  11. For one thing, DPI and 125%, 150% scaling are two different things. I have a monitor that has 192 DPI. That means 200% scaling is “normal”, just like 100% scaling is normal for a 96 DPI monitor. The apps come out the same size on the screen. On my monitor, setting it to 125% would make things microscopic.

    If you change the scaling in Windows settings because you are blind and want things bigger, that’s a different story. No matter what you set  your Windows scaling to, 150% or 300%, the DPI is always the same. As far as I know, there is no Windows function to get the users screen scaling value.

    Also, I don’t know whats going on with the Delphi IDE because it looks like it’s not DPI aware at all.