summaryrefslogtreecommitdiff
path: root/documentation/src/drawing.dox
diff options
context:
space:
mode:
authorManoloFLTK <41016272+ManoloFLTK@users.noreply.github.com>2020-03-26 06:29:25 +0100
committerManoloFLTK <41016272+ManoloFLTK@users.noreply.github.com>2020-03-26 06:29:25 +0100
commit89449280dc6be1d0d54359d48fc74d6c05f0c0c0 (patch)
tree86ba7d499866a39e11f2a6bd3361c8dc3ea0ef5d /documentation/src/drawing.dox
parentabe1c4f7c02675e784d9489d70fb79c8c8bc4608 (diff)
Doc: more details about initialisation of display scale factors.
Diffstat (limited to 'documentation/src/drawing.dox')
-rw-r--r--documentation/src/drawing.dox5
1 files changed, 4 insertions, 1 deletions
diff --git a/documentation/src/drawing.dox b/documentation/src/drawing.dox
index 6213d47ee..f40cbb9c1 100644
--- a/documentation/src/drawing.dox
+++ b/documentation/src/drawing.dox
@@ -70,7 +70,10 @@ to two pixels.
</ul>
At application start time, FLTK attempts to detect the adequate scale factor value for
-each screen of the system. If this attempt fails, it's possible to set the
+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.
+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
(e.g., 1.75) and any FLTK app will start scaled with that value. Furthermore,
it's possible to change the scale factor value of any screen at run time