Clarify Fl_Window::damage(uchar) handling - seems confused/wrong? ORing value doesn't match setting behaviour in FL_Widget.H!
Clarify Fl_Widget::test_shortcut() explanations. Fl_Widget.h says Internal Use only, but subclassing chapter gives details!
add an Fl_Draw_Area_Cb typedef to allow fl_scroll(...) to be doxygenated?
This method should eventually be removed in 1.4+
This method should eventually be removed in 1.4+
Refactor the doxygen comments for Fl_Button type() documentation.
Refactor the doxygen comments for Fl_Button when() documentation.
Refactor Fl_Chart::type() information.
Refactor the doxygen comments for Fl_Counter type() documentation.
we need to handle hidden hyphens and tabs here!
we handle all styles and selections
we must provide code to get pixel positions of the middle of a character as well
FIXME : get set methods pointing on shortcut_ have no effects as shortcut_ is unused in this class and derived!
FIXME : get set methods pointing on shortcut_ have no effects as shortcut_ is unused in this class and derived!
What does this do and how is it useful? Column numbers mean little in this context. Which functions depend on this one?
Unicode?
The user data value must be implemented using intptr_t or similar to avoid 64-bit machine incompatibilities.
The user data value must be implemented using intptr_t or similar to avoid 64-bit machine incompatibilities.
explain which system parameters are set up.
Check if we can remove resetting the current group in a later FLTK version (after 1.3.x). This may break "already broken" programs though if they rely on this "feature".
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.
FL_Button and FL_key... constants could be structured better (use an enum or some doxygen grouping ?)
Do we need this info about planes?
Work through the code and this documentation to harmonize the [OksiD] and [fltk2] functions.
Verify 16/24 bit Unicode limit for different character sets? OksiD's code appears limited to 16-bit whereas the FLTK2 code appears to handle a wider set. What about illegal characters? See comments in fl_utf8fromwc() and fl_utf8toUtf16().