Open akoch-yatta opened 4 months ago
@amartya4256 did you cover all places of that or are some still missing?
@amartya4256 did you cover all places of that or are some still missing?
Still working on it.
Here we need to think about how we are gonna replace these calls from the places where the objects are initialized. One alternative could be using the primary monitor zoom from the device but it might have some issue with threads. Must have a follow up on this @akoch-yatta @HeikoKlare
Does anyone know if there is a actually PR for this issue? If yes, please link it here.
The state "In Review" means that there is a PR, but it seems to me that this issue needs further discussion and should be moved to "New" until a decision on how to proceed has been made.
WDYT @akoch-yatta / @HeikoKlare ?
https://github.com/eclipse-platform/eclipse.platform.swt/pull/1401 is related to a different issue as it is supposed to replace the zoom value "correction" for non-image contexts and not to replace static usage of (native)DeviceZoom from DPIUtil, isn't it, @akoch-yatta?
Next step: document and investigate usages of these methods
To get rid of the static device zoom in DPIUtil, we should get rid of all remaining calls to:
Important: problematic is that Display::getDeviceZoom() calls getPrimaryMonitor() that will throw an exception when called from another thread