summaryrefslogtreecommitdiff
path: root/documentation/src
diff options
context:
space:
mode:
authorManoloFLTK <41016272+ManoloFLTK@users.noreply.github.com>2020-04-05 10:04:24 +0200
committerManoloFLTK <41016272+ManoloFLTK@users.noreply.github.com>2020-04-05 10:04:24 +0200
commitd503f5d3928adcc436c2bf1c8d6427736a512215 (patch)
tree47bffce4026ac139d1c70898c6c53e949b8e2ca4 /documentation/src
parente8185abf222014abb57138f78c18c8fbcbd27380 (diff)
Fix small typo.
Diffstat (limited to 'documentation/src')
-rw-r--r--documentation/src/drawing.dox2
1 files changed, 1 insertions, 1 deletions
diff --git a/documentation/src/drawing.dox b/documentation/src/drawing.dox
index f40cbb9c1..d49518a5f 100644
--- a/documentation/src/drawing.dox
+++ b/documentation/src/drawing.dox
@@ -84,7 +84,7 @@ Under Mac OS X, the corresponding GUI scaling shortcuts are ⌘/+/-/0/.
GUI rescaling involves also image drawing: the screen area covered by the drawn image
contains a number of pixels that grows with the scale factor. When FLTK draws images,
it maps the image data (the size of these data is given by Fl_Image::data_w() and
-Fl_Image::data_h())) to the screen area whose size (in FLTK units) is given by
+Fl_Image::data_h()) to the screen area whose size (in FLTK units) is given by
Fl_Image::w() and Fl_Image::h(). How exactly such mapping is performed depends on the
image type, the platform and some hardware features. The most common
case for Fl_RGB_Image's is that FLTK uses a scaled drawing system feature that directly