MySQL Bugs: #48867: MySQL Workbench is not dpi-aware

Bug #48867	MySQL Workbench is not dpi-aware
Submitted:	18 Nov 2009 15:37	Modified:	22 Jul 2010 7:26
Reporter:	Farid Zidan (Candidate Quality Contributor)	Email Updates:
Status:	Verified	Impact on me:	None
Category:	MySQL Workbench	Severity:	S2 (Serious)
Version:	5.2	OS:	Windows (XP SP3)
Assigned to:		CPU Architecture:	Any
Tags:	qc

Description:
MySQL Administrator application is not dpi-aware. On high resolution monitor (0.25 mm dot pitch) the application is not usable

How to repeat:
Start MySQL Administrator on Windows XP at 200% dpi setting (Display, Settings, Advanced, Custom DPI, 200%). Menu is automatically scaled by Windows, MySQL Administrar UI does not scale. 

Suggested fix:
Add dpi-awareness to MySQL Administrator

Zoom out attached jpg to 50% or less until menu text appears normal on your display to see what MySQL Administrator UI looks like on high-dpi monitor (2560x1600)

Thank you for the problem report.

Many thanks for writing a bug report. We are on the way to implement full functionality of MySQL Administrator into MySQL Workbench. We won't fix this anymore.

More informations about MySQL Workbench you will find here:

http://dev.mysql.com/workbench/

Workbend 5.2 is not dpi-aware. Zoom out attached jpeg to 50% or less until menu text appears normal on your machine. Other places in Workbench at 200% dpi on Windows XP some button text and UI elements are cut off

Workbend UI at 2560x1600 at 200% dpi on Windows XP

Attachment: workbench_dpi.jpg (image/jpeg, text), 176.63 KiB.

Changed Synosis from MySQL Administrator to MySQL Workbench

Changed incorrect status; "won't fix" was set based on Administrator, not workbench. Verified for workbench based on attached image, though needs to be checked against latest release.

bug #71675 and bug #73614 are duplicates

In Windows 7, everything is blurry on 101% (97 DPI) and the high DPI checkbox on the compatibility tab n the Windows program properties dialog is disabled.

Screenshot

Attachment: Schermata da 2016-02-04 14-30-51.png (image/png, text), 171.86 KiB.

Same problem here on an ASUS Zenbook UX501 with Fedora 23.

Ubuntu 16.04 - Get the magnifying glass!

Attachment: Screenshot from 2016-03-10 09-30-49.png (image/png, text), 107.28 KiB.

Bug #81971 marked as duplicate of this

Bug #83036 marked as duplicate of this

Ubuntu 16.04.1 - this is still an issue on a 4k monitor. Bug report shows the last time this was modified was in 2010. Is this bug going to get fixed?

MySQL Workbench is completely unusable on Ubuntu 16.04 with HiDPI. Fonts are unreadable and text blocks are cut off mid sentence

I've switched to DBeaver whilst this 7 year old bug is left unfixed

Bug #83555 marked as duplicate of this one

Bug #79980 marked as duplicate of this one

S2 (Serious) Since 2009! Is this open source or do I need to look elsewhere?

Linux 18.04 GC has deleted this obsolete software from my pc. Bye.

Bug #97629 marked as duplicate of this one

This still isn't working properly ten years later in Workbench 8. It should be easy to reproduce if you set your monitor to scaled other than 100%.

I'm having this issue on a Thinkpad T570 running Linux Mint 11+ years after this ticket was opened. Please fix this, 4k laptop monitors are becoming more common.

12 years later, the DPI issue STILL hasn't been fixed. C'mon dev team! You need to fix this so the software looks "professional"! Right now, it looks like a piracy software written by one man from the black market, not at all like a software written by such a big tech company!

On the same machine from my previous comment I'm able to use the Fractional Scaling feature set to 200% to achieve HiDPI without breaking Workbench. This is a hack and fractional scaling comes with its own set of quirks, but for anyone looking for a workaround this might help.

Regarding the workaround from my previous comment, after upgrading to Ubuntu 22 this is no longer a viable option. The lack of progress on this issue has caused my team to lose faith in this product, which had been the main reason we were still choosing mysql over postgresql. We've sourced an alternative open source visual schema editing tool for postgres and are in the process of converting our application boilerplates to use postgres. I dont know why Oracle has abandoned modern Linux support for this application but for us, that's a deal breaker. Thanks for the good years.