summaryrefslogtreecommitdiffstats
path: root/doxygen
diff options
context:
space:
mode:
authorSven Gothel <[email protected]>2020-01-04 17:18:02 +0100
committerSven Gothel <[email protected]>2020-01-04 17:18:02 +0100
commit7d7d4e4f194ed25dc8b450e13ab67020c607445b (patch)
tree2b1cd05475a6610af16fa9a0b3a876325c02fe35 /doxygen
parentfb211581fefc994d1458a2a74801dfb937170f39 (diff)
Bug 1358: MacOS NEWT WindowDriver / NewtCanvasSWT High-DPI:
Even w/ commit fb211581fefc994d1458a2a74801dfb937170f39, propagating the SWT pixelScale to NEWT-Child, hasPixelScale was never updated via updatePixelScale() through native callback [NSView viewDidChangeBackingProperties]! [NSView viewDidChangeBackingProperties] not being called on [created] child windows (NewtCanvasSWT) confused the overal pixelScale state, i.e. no hasPixelScale update via updatePixelScale(..). This change explicitly queries OSXUtil.GetWindowPixelScale(handle) (commit e6d53e29f05a6928192f6c4a988b2aa558be8d65)for: 1) updateMaxScreenPixelScaleByWindowHandle(..), which now updates the actual hasPixelScale after native creation and for 2) setSurfaceScale(..), which directly calls updatePixelScale(..) with the queried actual pixelScale instead of relying on the native callback [NSView viewDidChangeBackingProperties].
Diffstat (limited to 'doxygen')
0 files changed, 0 insertions, 0 deletions