Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
High DPI open issues
Revision as of 11:33, 23 February 2016 by Unnamed Poltroon (Talk)
Open issues for bug 399786 in http://git.eclipse.org/c/platform/eclipse.platform.swt.git/log/?h=slakkimsetti/HighDPIChangesforNeon
| Problem | Platform | Owner | Status | |
|---|---|---|---|---|
| 1 | Status line . The position of right side status like writable/gc condition not appearing correctly | |||
| 2 | ImageBasedFrame from platform UI nor rendering correctly | |||
| 3 | In tasklist view the help button is out of the task view boundary | |||
| 4 | The error icon for compilation unit is not correct if the class is abstract also the icon is cut on the top and bottom | |||
| 5 | Splash screen is clipped - size wrong | |||
| 6 | Dynamic change of scaling factor: SWT should adapt automatically | GTK3 | ||
| 7 | At 200% zoom, StyledText#computeSize(..), Link#computeSizeInPixels(...), etc. often throw an IAE. Example: Search > Java... . The problem is that clients expect TextLayout#getWidth() to return -1 if wrapping is disabled. This should:
|
GTK3 200% | ||
| 8 | Would be good to have a way to enforce a given zoom level for debugging purposes. E.g. on Ubuntu 14.04, I couldn't set the scale factor to 2 when I only had a 1680x1050 display attached. I hacked DPIUtil#setDeviceZoom(int) to add a system property "org.eclipse.swt.internal.deviceZoom", but this still left the rendered fonts unzoomed. | All | ||
| 9 | APIs: eliminate all unnecessary API additions like TextLayout#getWidthInPixels() | GTK3 |