Forum Discussion
Power BI Desktop canvas resolution issue
- 8 years ago
As it turns out it is a scaling issue. And it can be "solved" by setting the same level of scaling for both screens (in Windows at least):
Sorry for the czech language in the screenshot - Control Panel -> Appearance And Personalization -> Display -> Let me choose one scaling level for all my displays. Not a best solution, but it works for now.
- SamTrexler6 years agoHelper IV
Alex_Ooi I agree, it's messed up in the September 2019 release. It worked fine in the June 2019 release, installed using the msi file (x64, English). But using the exe installer with the July 2019 release the problem showed up.
I have used Desktop successfully on my laptop for a couple of years, with two additional monitors connected. I have each of the monitors set to the "Recommended" scaling - 125% on the laptop display, 100% on the 23-inch and 27-inch monitors - all of them 192x1080. Everything worked fine in the June 2019 release - dragging it between screens showed everything properly instantaneously, and I gained extra screen real estate on the larger monitors.
Starting with the July 2019 release, the screen is nearly unreadable on the 23-inch or 27-inch monitor at recommended scaling (100%) - text is broken and blotchy, in the panes as well as the canvas. Changing the monitor to 125% scaling (same as the main display) makes the screen readable, but now everything is large and I've lost the additional work area I rely on.
This is not good. Is there a better solution? I am going back to the June 2019 realease for now, even though I will lose some great new features like icon sets and grouping.
- Alex_Ooi6 years agoHelper IV
SamTrexler Can you show me a link on how I am able to revert to June 2019 version please?
- SamTrexler6 years agoHelper IV
Alex_Ooi I still had the June 2019 version in my downloads folder. So I just uninstalled the September version and ran the msi file to install the June version.
I don't know if there's a place where you can go to get the previous version. With all of the people being affected so significantly, maybe Microsoft should post a link to a version that works properly, until they get this fixed?