diff options
| author | Greg Ercolano <erco@seriss.com> | 2014-03-10 14:28:27 +0000 |
|---|---|---|
| committer | Greg Ercolano <erco@seriss.com> | 2014-03-10 14:28:27 +0000 |
| commit | 3d8c3577cbb2dd619f255f4e391d0d155c881b94 (patch) | |
| tree | 949c347321bfe4e334cdff3fa2a03fc5272624e9 /documentation/src/events.dox | |
| parent | 1ce59d2caadef759bfa4b608c01cf2243c9c208a (diff) | |
We need to add some details about repeating keys to the keyboard events docs.
Inserting this todo item to later be replaced with something more specific.
git-svn-id: file:///fltk/svn/fltk/branches/branch-1.3@10117 ea41ed52-d2ee-0310-a9c1-e6b18d33e121
Diffstat (limited to 'documentation/src/events.dox')
| -rw-r--r-- | documentation/src/events.dox | 2 |
1 files changed, 2 insertions, 0 deletions
diff --git a/documentation/src/events.dox b/documentation/src/events.dox index b9ba877e3..a6234d25a 100644 --- a/documentation/src/events.dox +++ b/documentation/src/events.dox @@ -172,6 +172,8 @@ currently has focus. This is not necessarily the same widget that received the corresponding \p FL_KEYDOWN event because focus may have changed between events. +\todo Add details on how to detect repeating keys, since on some X servers a repeating key will generate both FL_KEYUP and FL_KEYDOWN, such that to tell if a key is held, you need Fl::event_key(int) to detect if the key is being held down during FL_KEYUP or not. + \subsection events_fl_shortcut FL_SHORTCUT If the Fl::focus() widget is zero or ignores an \p FL_KEYBOARD event |