You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
- Create new variants lazily when needed for rendering at another zoom.
197
197
198
198
`Font` does not apply this pattern internally within the class, but instead uses the `SWTFontProvider` to get matching `Font` instances for a required zoom.
199
-
Access to an OS handle is usually provided via a public static non-API method like `Cursor#win32_getHandle(Cursor, zoom)`.
199
+
Access to an OS handle is usually provided via a public static non-API method like `Cursor.win32_getHandle(Cursor, zoom)`.
- a widget's parent is changed via `Control#setParent` (immediate consistency is required)
229
+
- a widget's parent is changed via `Control.setParent` (immediate consistency is required)
230
230
- a `Composite` has *no* layout manager and delegates changes to its children (geometry must remain stable during recalculation)
231
231
- immediate consistency is required (layout recalculation, cached geometry updates)
232
232
@@ -452,7 +452,7 @@ Be aware that `Rectangle.OfFloat` or `Point.OfFloat` are internal classes which
452
452
453
453
Windows differentiates between process and thread DPI awareness.
454
454
The process DPI awareness is defined by the executable, e.g. eclipse.exe will start with DPI awareness *System*, all recent javaw.exe will start with DPI awareness *PerMonitorV2*.
455
-
SWT will set the thread DPI awareness to *PerMonitorV2***if and ony if** monitor specific scaling is activated, either via `Display#setMonitorSpecificScaling` or the `swt.autoScale.updateOnRuntime` system property.
455
+
SWT will set the thread DPI awareness to *PerMonitorV2***if and ony if** monitor specific scaling is activated, either via `Display.setMonitorSpecificScaling` or the `swt.autoScale.updateOnRuntime` system property.
456
456
If:
457
457
458
458
- process and thread DPI awareness are the same, the application should always behave as expected
0 commit comments