Mirrors_UI_SDK/fltk
1
0
Fork 0
mirror of https://github.com/fltk/fltk.git synced 2026-05-21 22:51:41 +08:00
Code Issues Actions 3 Packages Projects Releases Wiki Activity

documented the major code changes in migration_1_3.dox

Browse Source 
git-svn-id: file:///fltk/svn/fltk/branches/branch-1.3@6470 ea41ed52-d2ee-0310-a9c1-e6b18d33e121
This commit is contained in:
Albrecht Schlosser
2008-10-19 14:24:35 +00:00
parent 488ee44257
commit 68c34f9ec9
1 changed files with 51 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files
documentation/src/migration_1_3.dox
+51 -5
View File
@@ -5,16 +5,62 @@
This appendix describes the differences between the FLTK
1.1.x and FLTK 1.3.x functions and classes.
\section migration_1_3_fltk_1_0 Migrating From FLTK 1.0
If you want to migrate your code from FLTK 1.0 to FLTK 1.3,
then you should also consult Appendix \ref migration_1_1.
then you should first consult Appendix \ref migration_1_1.
\section migration_1_3_fl_scroll Fl_Scroll Widget
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
Fl_Widget::position(int,int), but with a completely different function (moving
the scrollbars instead of moving the widget).
Please be aware that you need to change your application's code for all
Fl_Scroll-derived widgets, if you used Fl_Scroll::position(int x, int y)
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).
\section migration_1_3_unicode Unicode (utf-8)
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.
\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.
Fl_Widget::x(), Fl_Widget::y(), Fl_Widget::w(), Fl_Widget::h(), from
short (16-bit) to int (32-bit) representation. This should not affect
any existing code, but makes it possible to use bigger scroll areas
(e.g. Fl_Scroll widget).
\htmlonly
<hr>
<a class="el" href="index.html">[Index]</a> &nbsp;&nbsp;
<a class="el" href="migration_1_1.html">[Previous]</a>&nbsp;
\ref migration_1_1 &nbsp;&nbsp;
<a class="el" href="development.html">[Next]</a>&nbsp;
\ref development
<a class="el" href="migration_1_1.html">[Previous] &nbsp;
H - Migrating Code from FLTK 1.1 to 1.3</a> &nbsp;&nbsp;
<a class="el" href="development.html">[Next] &nbsp;
I - Developer Information</a>
\endhtmlonly
*/