Author: engelsman Date: 2009-06-27 09:22:27 -0700 (Sat, 27 Jun 2009) New Revision: 6797 Log: minor changes and typo corrections in migration_1_3.dox
Modified: branches/branch-1.3/documentation/src/migration_1_3.dox Modified: branches/branch-1.3/documentation/src/migration_1_3.dox =================================================================== --- branches/branch-1.3/documentation/src/migration_1_3.dox 2009-06-27 15:19:04 UTC (rev 6796) +++ branches/branch-1.3/documentation/src/migration_1_3.dox 2009-06-27 16:22:27 UTC (rev 6797) @@ -15,7 +15,7 @@ Fl_Scroll::scroll_to(int x, int y) replaces Fl_Scroll::position(int x, int y). -This change was needed, because Fl_Scroll::position(int,int) redefined +This change was needed because Fl_Scroll::position(int,int) redefined Fl_Widget::position(int,int), but with a completely different function (moving the scrollbars instead of moving the widget). @@ -24,27 +24,27 @@ to position <b>the scrollbars</b> (not the widget itself). The compiler will not detect any errors, because your calls to -\b \e position(int x, int y) will be calling Fl_Widget::position(int x, int y). +\b position(int x, int y) will be calling Fl_Widget::position(int x, int y). -\section migration_1_3_unicode Unicode (utf-8) +\section migration_1_3_unicode Unicode (UTF-8) -FLTK 1.3 uses Unicode (utf-8) encoding internally. If you are only using +FLTK 1.3 uses Unicode (UTF-8) encoding internally. If you are only using characters in the ASCII range (32-127), there is a high probability that you don't need to modify your code. However, if you use international characters (128-255), encoded as e.g. Windows codepage 1252, ISO-8859-1, ISO-8859-15 or any other encoding, then you will need to update your character string constants and widget input data accordingly. +Please refer to the \ref unicode chapter for more details. + \note It is important that, although your software uses only ASCII characters for input to FLTK widgets, the user may enter non-ASCII characters, and FLTK will return these characters with utf-8 encoding to your application, e.g. via Fl_Input::value(). You \b will need to re-encode them to \b your (non-utf-8) encoding, otherwise you might see or print garbage in your data. -\link unicode For more information see here.\endlink - \section migration_1_3_int_coords Widget Coordinate Representation FLTK 1.3 changed all Widget coordinate variables and methods, e.g. _______________________________________________ fltk-commit mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-commit
