Recommended Posts

Samsung presented a model 13.3 "with Windows 8 (the prototype) with a resolution of 2560x1440.

And Acer has released in 2013 a notebook with resolution 2880 * 1620

http://www.pcworld.com/article/2024391/acer-takes-on-apple-with-retina-class-laptop-displays.html

But I wonder if they do not expect the Windows Blue (hoping they will find a way to take better care of these types of screens) in order to get their products.

With the current state of Windows, it is difficult to bear such screens. (Between blurry fonts or DPI not upscaled).

Apple has anticipated the thing and allowed developers to update their applications. But if Windows is interested in something then it goes to the democratization of the Retina in the PC.

Had a response back from LogMeIn on DPI scaling issues:

servlet.ImageServer?id=01530000000qEt5&oid=00D300000006VGf

Hello ,

Thank you for contacting LogMeIn.

I would be happy to address your question. This is a known issue with Server 2012 and Windows 8. I am adding your example to a parent ticket and you will be notified via email when we have a permanent solution to this problem.

New capture :)

Adobe Reader XI (font blur) : http://d.pr/i/XiRR - Adobe Reader XI Install (very small) : http://d.pr/i/fL58

Skype 6.1 (font blur) : http://d.pr/i/ak81- http://d.pr/i/REpH

Mumble (optimized half)

: http://d.pr/i/w5Ew - http://d.pr/i/eFjY

Viscosity 1.4 (font & image blur) : http://d.pr/i/VKZU - http://d.pr/i/C1Gq

Java (panel Control WT*) : http://d.pr/i/Rp5g

Word (good) : http://d.pr/i/YXv9

Visual Studio 2012 : http://d.pr/i/s4I1 (well designed but the window for the developer license is not optimized against)

Nvidia Control Panel (Not optimize) : http://d.pr/i/t5dR and Update Nvidia (font blur) : http://d.pr/i/K4FE

CCleaner (font blur) : http://d.pr/i/cy2l - http://d.pr/i/zhht - http://d.pr/i/6qtY

IE 10 : http://d.pr/i/oeus - http://d.pr/i/lIPt (don't know x2 reproduce images with a resolution and DPI to 200%. Apple images are blurred as Youtube logo)

Origin update (font blur) : http://d.pr/i/5rHF

Intel Rapid (Good) : http://d.pr/i/2Tw7

Windows UI (Good) : http://d.pr/i/yVCn - http://d.pr/i/jzNb - http://d.pr/i/v3zx - http://d.pr/i/mK4C - http://d.pr/i/2L6j - http://d.pr/i/8nF5 - http://d.pr/i/skBP - http://d.pr/i/SZMD - http://d.pr/i/fRxj - http://d.pr/i/koId - http://d.pr/i/ZrVK

Here I made a few catches to show the shortcomings of the resolution to 200%. The workstation and the control panel is well optimized but for those who is software that is not the case.

Some say that we must reduce the DPI 200 DPI but have a rMBP it's nice and no need to paste the screen.

  • Like 2

Sadly both Nvidia and AMD haven't given a thought to DPI scaling on their control panels which is ironic because Intel have (whether accidental or intended).

When I recovered this problem to Nvidia I was referred to this page and I had to be my DPI 140 and 180. And returned the blame on Windows.

Support Nvidia not doing their job.

http://blogs.msdn.com/b/b8/archive/2012/03/21/scaling-to-different-screens.aspx

When I recovered this problem to Nvidia I was referred to this page and I had to be my DPI 140 and 180. And returned the blame on Windows.

Support Nvidia not doing their job.

http://blogs.msdn.co...nt-screens.aspx

Yes, they are not. That link talks about scaling in Metro. I have to say, scaling in Metro works fabulously but the catch is there are only two levels - 140 and 180. There are some cases where 120 would have been useful, like say 1920x1080 on 13.3 inches. There 100% is too small but 140% (forced through Ease of Access) is too big!

Desktop is a completely different thing altogether, and that is mostly what we are discussing here. It works well for apps that support it, but for some like Nvidia CP it's a right mess. The advantage over Metro is you can of course choose your exact scaling rather than just relying on 140 or 180 as in Metro. IMO they should allow more control over the Metro if possible and coax developers into updating their desktop apps.

Yes, they are not. That link talks about scaling in Metro. I have to say, scaling in Metro works fabulously but the catch is there are only two levels - 140 and 180. There are some cases where 120 would have been useful, like say 1920x1080 on 13.3 inches. There 100% is too small but 140% (forced through Ease of Access) is too big!

Desktop is a completely different thing altogether, and that is mostly what we are discussing here. It works well for apps that support it, but for some like Nvidia CP it's a right mess. The advantage over Metro is you can of course choose your exact scaling rather than just relying on 140 or 180 as in Metro. IMO they should allow more control over the Metro if possible and coax developers into updating their desktop apps.

I think that will happen as they mature the metro side itself. As for the desktop, it's clear that the app developers have to update their stuff for higher dpi and not just lay blame on windows for what really is in the end their own laziness.

Yes, they are not. That link talks about scaling in Metro. I have to say, scaling in Metro works fabulously but the catch is there are only two levels - 140 and 180. There are some cases where 120 would have been useful, like say 1920x1080 on 13.3 inches. There 100% is too small but 140% (forced through Ease of Access) is too big!

Desktop is a completely different thing altogether, and that is mostly what we are discussing here. It works well for apps that support it, but for some like Nvidia CP it's a right mess. The advantage over Metro is you can of course choose your exact scaling rather than just relying on 140 or 180 as in Metro. IMO they should allow more control over the Metro if possible and coax developers into updating their desktop apps.

If I use the 140 (it is very small) and 180 (small). A 200 is about right (You do not need a hand lens on 15"). Use 180 on 24" or 27" no problem but a 15" the difference is quickly noticed.

I wish people would stop referring to high DPI as reitna as if Apple invented high DPI though.

Nobody said otherwise. Windows uses the DPI when Apple uses Retina.

  • 4 months later...

Microsoft really needs to move over to vector art and allow users to freely scale the interface to their choosing (within reason) - by default it should scale according to physical size. Icons that currently change appearance dependent upon their size could be handled with transition points. Not only is such a change important for high-DPI displays but it's even an issue at the moment:

30" - 101 DPI - 2560x1600

27" - 109 DPI - 2560x1440

24" - 94 DPI - 1920x1200

22" - 90 DPI - 1680x1050

That means the Windows UI changes physical size depending on the display that you have, which is terribly inconsistent. By default Windows 8 uses 125% scale for my 30" display, which makes everything appear too large. Therefore I prefer to use 100% scale, which is a bit smaller than I would like. Using a custom scale looks terrible, as icons appear aliased and UI elements don't scale smoothly.

Apple has a huge advantage over Microsoft in that it controls the hardware as well as the software. Microsoft's only option is to implement a more flexible approach and vector art is the obvious way to achieve that. There was talk that Microsoft was working on this years ago - back when Vista was still in development - but unfortunately it was dropped. Now Microsoft has fallen behind. Metro is designed with alternative DPIs in mind but unfortunately it's not a replacement for desktop applications.

+1

For the record... and maybe someone already posted this, but Parallels uses a DPI of 199 and that works fair in Win 8.

This topic is now closed to further replies.
  • Posts

    • The problem isn't with Epic, it's with the platform holders like Steam and Nintendo, they should be a lot more strict in their review process.
    • Hello, Installed here without issue. Regards, Aryeh Goretsky
    • Microsoft updates Visual Studio Code with easier language model discovery and in-app search by Paul Hill Microsoft has released Visual Studio Code 1.125, its latest weekly release. This week, the company has focused on discovering and installing extra language models via the Marketplace; searching the web and securely browsing over remote connections without leaving VS Code; choosing how long VS Code waits before installing extension updates; and delivering managed Copilot settings through existing device management tooling. In older versions of VS Code, extensions could contribute their own model providers, but to find these extensions, you needed the right tags to search for in the Extension view. Now, the Language Models editor gives you an Install Model Providers button that opens the Extensions view, which is filtered to extensions that contribute model providers, making it easier to find and install them. Once you install a provider, its model will appear in the model picker. If you use the integrated browser much, you can now look up information without leaving VS Code by typing a query into the integrated browser’s address bar. It will use your configured search engine, the same way a standalone browser does. You can use workbench.browser.searchEngine to pick a search engine. When the browser is opened in a remote workspace, it's now possible to proxy HTTP(S) traffic via the remote connection. This allows you to connect to any ports or services that can only be accessed from the remote machine. If you read our coverage from two weeks ago about VS Code 1.123, you might have seen that extension updates have a two-hour delay as a safety measure. In this update, Microsoft is giving you the ability to configure the time of the delay. You can find it under extensions.autoUpdateDelay. Finally, with this update, admins can deliver managed GitHub Copilot settings through native device management (MDM) channels on Windows and macOS, in addition to account-based enterprise settings files. Settings delivered via MDM appear as policy-enforced in VS Code and can’t be overridden locally. Future updates will extend the supported policy keys across Copilot surfaces. You can download the update from the Visual Studio Code website now.
    • "it opens up new doors for people who prefer using Edge, but cannot be bothered to configure a Microsoft account" You already have a Microsoft account if you are using Windows 11, because you can't set it up without one.
    • This is how much iPhone 18 Pro could cost after Apple's price hike confirmed by Hamid Ganji Image via Apple Apple CEO Tim Cook confirmed in a recent interview that the company may have to raise prices on some of its products due to the ongoing memory shortage. While he did not elaborate on the scale of the price hikes, new estimates suggest that Pro iPhone models could become significantly more expensive this fall. The Wall Street Journal and research firm TechInsights have come up with an educated estimate of how much the upcoming iPhone 18 Pro could cost after its launch in September. The estimate is based on current increases in memory and storage chip prices. For starters, the iPhone 18 Pro base model is expected to feature 12GB of RAM and 256GB of internal storage. According to TechInsights estimates, 12GB of DRAM for the iPhone 17 Pro cost Apple $39 last year. However, for the iPhone 18 Pro, the cost of the same amount of DRAM could soar to $145. Likewise, 256GB of flash storage that previously cost $13 could now cost around $51. Producing a base iPhone 17 Pro reportedly cost Apple around $582, but TechInsights estimates that the production cost of the iPhone 18 Pro could rise to $726. If Apple wants to maintain the roughly 47% profit margin it enjoys on the iPhone 17 Pro, the base price of the iPhone 18 Pro would need to reach $1,371. After standard pricing adjustments, customers could end up paying around $1,299 for the base model. However, that may not be the end of the story. As we previously reported, the iPhone 18 Pro is said to feature a variable-aperture lens, which could cost Apple at least 50% more than the current camera system. The estimated $1,299 price tag does not include the additional cost of this upgraded camera hardware. Once that expense is factored in, the base model could cost at least $1,399. A $1,399 price tag for the base iPhone 18 Pro would represent a significant increase over the current $1,099 starting price of the iPhone 17 Pro. If Apple wants to keep its upcoming iPhones competitive, it may need to accept lower profit margins.
  • Recent Achievements

    • Week One Done
      Classifyskilleducation earned a badge
      Week One Done
    • One Month Later
      eurospharma62 earned a badge
      One Month Later
    • Week One Done
      With What earned a badge
      Week One Done
    • Week One Done
      Harris Gilbert earned a badge
      Week One Done
    • One Month Later
      Vincian earned a badge
      One Month Later
  • Popular Contributors

    1. 1
      +primortal
      543
    2. 2
      +Edouard
      171
    3. 3
      PsYcHoKiLLa
      84
    4. 4
      ATLien_0
      64
    5. 5
      neufuse
      64
  • Tell a friend

    Love Neowin? Tell a friend!