summaryrefslogtreecommitdiff
path: root/src/Fl_compose.cxx
diff options
context:
space:
mode:
authorManolo Gouy <Manolo>2018-05-24 10:58:47 +0000
committerManolo Gouy <Manolo>2018-05-24 10:58:47 +0000
commitc886fe9c33e6894c2e70f07857b4c29cfa77d60a (patch)
treefbd701859293a05a2b706b074c65df27d7b22e25 /src/Fl_compose.cxx
parentaf3625eb209f68eccb5bd281f768aba606e8b811 (diff)
Add documentation for Fl::reset_marked_text() and Fl::insertion_point_location().
git-svn-id: file:///fltk/svn/fltk/branches/branch-1.4@12930 ea41ed52-d2ee-0310-a9c1-e6b18d33e121
Diffstat (limited to 'src/Fl_compose.cxx')
-rw-r--r--src/Fl_compose.cxx6
1 files changed, 3 insertions, 3 deletions
diff --git a/src/Fl_compose.cxx b/src/Fl_compose.cxx
index 8a65841a8..6d4aa9032 100644
--- a/src/Fl_compose.cxx
+++ b/src/Fl_compose.cxx
@@ -50,8 +50,8 @@ int Fl::compose_state = 0;
marked text, usually underlining it. Widgets can use
<tt>int Fl::compose_state</tt> <i>after</i> having called Fl::compose(int&)
to obtain the length in bytes of marked text that always finishes at the
- current insertion point. It's the widget's task to underline marked text.
- Widgets should also call <tt>void Fl::reset_marked_text()</tt> when processing FL_UNFOCUS
+ current insertion point. Widgets should also call
+ <tt>void Fl::reset_marked_text()</tt> when processing FL_UNFOCUS
events. Optionally, widgets can also call
<tt>void Fl::insertion_point_location(int x, int y, int height)</tt> to indicate the window
coordinates of the bottom of the current insertion point and the line height.
@@ -63,7 +63,7 @@ int Fl::compose_state = 0;
text input will work, but will not signal to the user what text is marked.
Finally, text editing widgets should call <tt>set_flag(MAC_USE_ACCENTS_MENU);</tt>
in their constructor if they want to use the feature introduced with Mac OS 10.7 "Lion"
- where pressing and holding a key on the keyboard opens an accented-character menu window.
+ where pressing and holding certain keys on the keyboard opens an accented-character menu window.
<p>Though the current implementation returns immediately, future
versions may take quite awhile, as they may pop up a window or do