Precision 7530 & Precision 7730 owner's thread

Not much, really. I just gently pressed it in, turned the driver a couple of times and noticed that the screw was threading in and down, so just carried on with the same pressure.

 

I had a busy couple of days, but today I took the panel out and snapped some pictures of the display cable on the back. I will also post these back in the first post in this thread. I figure that they could be useful down the line for anyone else considering a screen upgrade...

 

That'll do nicely. Thank you very very much.

 

Sorry I have to call you out on this one... yes a few of the legacy windows are still somewhat blurry, but honestly who gives a damn? How often are you using these parts and even so you can still read everything fine, you are just cherry picking in order to try a prove a point that doesn't really hold up.

Most of Windows 10 works great with HiDPI, scaling, laptop UHD panels, etc, and the parts that are a little blurry are legacy parts that you don't access often at all anyway. Does it really bother you so much that the Wi-Fi properties and mmc windows are a little blurry and that's a reason that you won't bother with a UHD panel?

And BTW I never get any constant prompts to 'fix blurry apps' every time the graphics adaptor changes, I set it once for each adaptor and it never bothered me again. You are doing something wrong...

 

Sorry what real issues? I've had UHD panels on three different 15.6" laptops since mid 2017 and I've experienced no real issues at all. Only some legacy windows are a little blurry but they are windows that you never access often at all.

 

I regularly run into business applications that are broken in high-DPI. Either everything is very tiny, or the layout is completely messed up in some way. Most of them you can fix by going to compatibility settings on the app, and telling Windows to override the scaling behavior with the "System" behavior. This will make them appear blurry, but they will be functional. (Though how is a "regular user" supposed to know to do this?) These are applications that "claim" to Windows to be high-DPI aware, but actually don't handle it properly.

Some are broken even with this. Example, the VMware vSphere client (version 5.5 or 6.0), and using it to access a remote VM's console. It is totally messed up, depending on how you configure it; either the menus/etc are broken, everything is very tiny, or click events don't occur where you actually click.

The implementation in Windows is more flexible than that of macOS (which only allows for two scaling ratios, 100% and 200%) but that makes support more cumbersome for developers at the same time. And apps that don't support high-DPI do indeed appear blurry, because they are rendered at a lower resolution and then scaled up (but this is the case on other platforms including macOS as well). At least on the Mac side, there doesn't seem to be this issue of apps falsely claiming high-DPI support and ending up tiny or with broken layouts. On the Windows side, both Microsoft and third-party developers have been making improvements here, but it is very slow-going... Though some of the broken business applications that I have encountered are produced by vendors who don't seem to really care at all about fixing this.

The fact that some built-in Windows control panels and such don't support high-DPI yet is a bit sad and unpolished on their part, but I wouldn't consider it a major issue, nothing there is actually broken.

 

I agree with all of what you said, and just to highlight the real issue is applications not catching up to HiDPI, not Windows 10 itself. That was the discussion, there is no real problem with Windows 10 and HiDPI, blame the applications that haven't bothered to catch up.

 

That's sort of a problem for people who have to use those applications, though, and we have a few issues going on with that at my office as we start to roll out high-DPI screens to a handful of "non-technical" users. People get frustrated because programs that use to work fine are now messed up just because the screen has been swapped out, and a (hard to discover) configuration tweak is needed to fix it. You can see how that wouldn't make any sense to people.

Not saying there's a good answer. I guess the best way to fix it would be for Microsoft to somehow collect and maintain a list of applications that falsely claim high-DPI support and automatically default them to "System" scaling (since that fixes almost all apps)... But, yuck.

Bottom line, if someone decides to side-step this issue for now by ordering a 1080p screen, and Dell is only offering a gimped 1080p screen, I totally get that frustration.

 

I completely understand that, though people should do more extensive research before buying, especially something so expensive. I know, I know, in an ideal world vendors shouldn't be cheap, obscure about tech specs, etc, but you have to protect yourself because that is the norm in today's corporate profit motive based world.

No one should rush into buy something without knowing for sure about the tech specs that are important to them. First by reading through all published Dell tech spec docs and possibly whitepapers, and if that doesn't provide answers, then second by being very patient and coming to sites like this to find out the information they need before buying.

 

I stayed at FullHD because my external monitors are 24" 1920x1200 and 2560x1440 so it looks good to me when all displays are set to 125% DPI. From my experience the trouble starts when you need different scalings per monitor and start to move an app from 200% (4K laptop screen) to 125% or alike. The per display aware HiDPI scaling is relatively new and not well supported by many apps. E.g. Visual Studio (up to now, they are working on that) will get blurry when you move it to a display which differs from the initial display scaling. IIRC Office 2016 can't do it either.

If the apps support that it is a funny moment to drag a window across displays and see how it scales up/down when fully on the other display, like e.g. Windows Explorer.