diff options
| author | ManoloFLTK <41016272+ManoloFLTK@users.noreply.github.com> | 2022-03-10 15:05:26 +0100 |
|---|---|---|
| committer | ManoloFLTK <41016272+ManoloFLTK@users.noreply.github.com> | 2022-03-10 15:05:26 +0100 |
| commit | 9d869d73c1ca8f6c884f528a3ad4f623f25dffb1 (patch) | |
| tree | eac9ea00fe50b10b054519a9f9775734a0a5b9b2 /documentation/src/drawing.dox | |
| parent | 9e4c7aa77cc9e68afe1d6865662410664eed02f7 (diff) | |
Begin documenting the Wayland platform, new in FLTK version 1.4
Diffstat (limited to 'documentation/src/drawing.dox')
| -rw-r--r-- | documentation/src/drawing.dox | 8 |
1 files changed, 6 insertions, 2 deletions
diff --git a/documentation/src/drawing.dox b/documentation/src/drawing.dox index 1eee9f195..a80286f68 100644 --- a/documentation/src/drawing.dox +++ b/documentation/src/drawing.dox @@ -69,11 +69,15 @@ The current scale factor value, for an Fl_Window named \e window, is given by One drawing unit generally corresponds to one screen pixel ... <li>... but not on macOS and for retina displays, where one drawing unit corresponds to two pixels. + +<li>... and not with the Wayland platform, where one drawing unit may +correspond to 1, 2, or 3 pixels according to the current value of the +Wayland-defined, integer-valued scale factor. </ul> At application start time, FLTK attempts to detect the adequate scale factor value for -each screen of the system. Here is how that's done under the \ref osissues_x_scaling "X11" -and \ref osissues_windows_scaling "Windows" platforms. +each screen of the system. Here is how that's done under the \ref osissues_x_scaling "X11", +\ref osissues_windows_scaling "Windows", and \ref osissues_wayland_scaling "Wayland" platforms. If the resulting scale factor is not satisfactory, and also under the macOS platform, it's possible to set the <tt>FLTK_SCALING_FACTOR</tt> environmental variable to the desired numerical value |