Summary: | UI does not correctly process X11 xrdb Xft.dpi resourse | ||||||
---|---|---|---|---|---|---|---|
Product: | [Eclipse Project] Platform | Reporter: | Kent Dorfman <kent.dorfman766> | ||||
Component: | SWT | Assignee: | Platform-SWT-Inbox <platform-swt-inbox> | ||||
Status: | NEW --- | QA Contact: | |||||
Severity: | normal | ||||||
Priority: | P3 | CC: | loskutov | ||||
Version: | 4.17 | Keywords: | needinfo | ||||
Target Milestone: | --- | ||||||
Hardware: | PC | ||||||
OS: | Linux | ||||||
Whiteboard: | |||||||
Attachments: |
|
Description
Kent Dorfman
2020-12-08 14:22:54 EST
Please attach what "About - Configuration Details" says. this doesn't work either: XAPPLRESDIR=/etc/X11/app-defaults RESOURCE_NAME=Eclipse /usr/local/eclipse/eclipse where the Eclpse resource file contains: *Xft.dpi: 48 Other Xfreetype apps work as expected. It's eclipse that is the PITA OK -- monetarilly... (In reply to Andrey Loskutov from comment #1) > Please attach what "About - Configuration Details" says. ok - in a few minutes Created attachment 284996 [details]
aout-config
per request
Could you just for fun check if may be 4.18 RC2 works better? For the record, here is what we get from the system: org.eclipse.swt.internal.deviceZoom=100 org.eclipse.swt.internal.gdk.backend=x11 org.eclipse.swt.internal.gtk.theme=darkgtk3 org.eclipse.swt.internal.gtk.version=3.24.5 GDK_DPI_SCALE=1 GDK_SCALE=1 The GDK symbols certainly affect the UI font sizes, but in a global manner, so very hackish to go that route in addressing the bug. The issue seems purely that the UI is not referencing the defined xresouce properly when it is contained within the C preprocessor blocks in the xrdb database. I don't have the internet resources to be downloading full eclipse installations on a trial and error basis. Due to its size and setup complexity for my use case I only download one release per year...unless I know of a critical feature patch that requires a complee download...so I'm more hesitance to install RC2 unless you know for certain that it fixes the issue. No, I don't *know for sure*, just guessing you might have luck with 4.18 because why not :) I fear your configuration is a very special one, so except you are willing to debug it yourself nothing will change. |