MySQL Bugs: #81003: Auto-scaling per DPI setting not working properly in 1.3.6 release

Bug #81003	Auto-scaling per DPI setting not working properly in 1.3.6 release
Submitted:	8 Apr 2016 3:21	Modified:	23 May 2019 19:52
Reporter:	luke lee	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL for Windows: MySQL for Excel	Severity:	S3 (Non-critical)
Version:	1.3.6	OS:	Windows (10 Pro, Excel 2016)
Assigned to:		CPU Architecture:	Any
Tags:	Automatic Scaling Excel2016

Description:
Automatic scaling on different DPI settings in 1.3.6 release does not seem to work well. 

Text sizes are way too small or way to big. 

I tried to re-size the pane but it only allows you to reduce it, not expand it. 

Tested machine spec, 

HP Zbook G3 Studio 4K display at 3840 x 2160, scaling % set to 250%. 

Running Excel 2016 Business 64 bit version. 

How to repeat:
HP Zbook G3 Studio 4K display at 3840 x 2160, scaling % set to 250%. 

Running Excel 2016 Business 64 bit version. 

goto Data tab, 

click MySQL for Excel, 

- Observe the text sizes
- try expanding the pane

Just a comment.

I think most vendors providing desktop applications for Windos struggle with the the handling of scaling in Windows with high resolution displays. Unlike Mac OS-X (and also ChromeOS BTW), Windows allows for a 'non-intergral' scaling factor (250% in your case). With Mac etc. only a 'integral' scaling factor (200%, 300% etc.) is possible. Various Linux desktops may differ in their concepts here, but at least I think Gnome does like Mac does.

Microsoft has this resource online: https://msdn.microsoft.com/en-us/library/windows/desktop/dn469266(v=vs.85).aspx (and in this respect there is no difference between Windows 8.1 and Windows 10). Reading this is mandatory for people who wamt to take part in this discussion IMO. :-) 

The most simple solution is to make the application totally "DPI-unaware". This should resolve all scaling problems (it does for us) as scaling will be handled 100% by Windows and not the application, but it may result in some 'blurriness' of small fonts in particular. 

In my eperience "0 % DPI-awareness" is a better solution than any other "DPI awareness level" that is not "100% DPI-aware". In other words: 100% is best 0% is second, Anything else causes issues. 

-- Peter
-- not a MySQL/Oracle person

Thank you for the bug report. Are you able to provide a screenshot?. Thanks.

ScreenShot

Attachment: Capture.PNG (image/png, text), 152.28 KiB.

Hello luke lee,

Thank you for your feedback.
Verified this behavior on MS Excel 2016, MySQL for Excel 1.3.6.

Thanks,
Chiranjeevi

Screenshots.

Attachment: 81003.zip (application/zip, text), 533.00 KiB.

Unusable

Attachment: Capture.PNG (image/png, text), 23.99 KiB.

How is this "Non-critical" and not updated after 2 years?

I am using a Lenovo Yoga 14" at 3840 x 2160 with Windows scaling at 300%, and the MySQL Excel add-in is completely unusable. 

Please see the screenshot I just posted. No amount of resizing is possible to fix this. I can scale down my resolution and reduce the Windows scaling to 100%, but then the $2K computer I just bought displays like a VGA from 10 years ago, which is a non-starter.

Will this ever be fixed? Is there a workaround to force the add-in to scale itself appropriately? I can't use the built-in Windows compatibility fix b/c the add-in isn't recognized as an executable, so Windows doesn't offer compatibility options.

Any updates on this 3 year old issue?

I have the same problem on a Windows 10 Dell XPS 15 9560 laptop. Are there any updates on this long-standing issue or is these bug reporting forums are just to show that "you care"? Thanks!

Posted by developer:
 
Fixed the automatic scaling of visual elements when the OS is configured with a DPI settings different than 100%.

Posted by developer:
 
Fixed as of the upcoming MySQL for Excel 1.3.8 release, and here's the changelog entry:

On Windows, the automatic scaling of visual elements did not work as
expected when the operating system was configured to use a DPI value other
than 100%.

Thank you for the bug report.