FLTK 1.3.0
|
Clarify Fl_Window::damage(n) 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!
work out why Fl::get_color() does not give links!
work out why these do not give links!
add an Fl_Draw_Area_Cb typedef to allow fl_scroll(...) to be doxygenated?
Refactor the doxygen comments for Fl_Button type() documentation.
Refactor the doxygen comments for Fl_Button when() documentation.
Refactor Fl_Check_Button doxygen comments (add color() info etc?)
Generate Fl_Check_Button.gif with visible checkmark.
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
What does this do and how is it useful? Column numbers mean little in this context. Which functions depend on this one?
Unicode?
Correct the incorrect logic where length of strings tested
Clarify whether n means number of bytes, or characters.
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().