mirror of https://github.com/fltk/fltk.git
Browse Source
The FLTK 1.0 compatibility support by defining macro 'FLTK_1_0_COMPAT' did no longer work since FLTK 1.3.x and nobody complained. Hence we can safely remove this "feature". Documentation changes: - Drop chapter 'Migrating Code from FLTK 1.0 to 1.1' - Drop chapter 'Migrating Code from FLTK 1.1 to 1.3' - Add chapter 'Migrating Code from FLTK 1.3 to 1.4' The removed chapters are still available in FLTK 1.3 docs.pull/48/head
Albrecht Schlosser
5 years ago
12 changed files with 70 additions and 297 deletions
@ -1,176 +0,0 @@ |
|||||||
/** |
|
||||||
|
|
||||||
\page migration_1_1 Migrating Code from FLTK 1.0 to 1.1 |
|
||||||
|
|
||||||
|
|
||||||
This appendix describes the differences between the FLTK |
|
||||||
1.0.x and FLTK 1.1.x functions and classes. |
|
||||||
|
|
||||||
\section migration_1_1_color Color Values |
|
||||||
|
|
||||||
Color values are now stored in a 32-bit unsigned integer |
|
||||||
instead of the unsigned character in 1.0.x. This allows for the |
|
||||||
specification of 24-bit RGB values or 8-bit FLTK color indices. |
|
||||||
|
|
||||||
\c FL_BLACK and \c FL_WHITE now remain black and white, even if |
|
||||||
the base color of the gray ramp is changed using Fl::background(). |
|
||||||
\c FL_DARK3 and \c FL_LIGHT3 can be used instead to |
|
||||||
draw a very dark or a very bright background hue. |
|
||||||
|
|
||||||
Widgets use the new color symbols \c FL_FOREGROUND_COLOR, |
|
||||||
\c FL_BACKGROUND_COLOR, \c FL_BACKGROUND2_COLOR, |
|
||||||
\c FL_INACTIVE_COLOR, and \c FL_SELECTION_COLOR. |
|
||||||
More details can be found in the chapter \ref enumerations. |
|
||||||
|
|
||||||
\section migration_1_1_cutnpaste Cut and Paste Support |
|
||||||
|
|
||||||
The FLTK clipboard is now broken into two parts - a local |
|
||||||
selection value and a cut-and-paste value. This allows FLTK to |
|
||||||
support things like highlighting and replacing text that was |
|
||||||
previously cut or copied, which makes FLTK applications behave |
|
||||||
like traditional GUI applications. |
|
||||||
|
|
||||||
\section migration_1_1_file_chooser File Chooser |
|
||||||
|
|
||||||
The file chooser in FLTK 1.1.x is significantly different |
|
||||||
than the one supplied with FLTK 1.0.x. Any code that directly |
|
||||||
references the old \c FCB class or members will need |
|
||||||
to be ported to the new Fl_File_Chooser class. |
|
||||||
|
|
||||||
\section migration_1_1_functions Function Names |
|
||||||
|
|
||||||
Some function names have changed from FLTK 1.0.x to 1.1.x in |
|
||||||
order to avoid name space collisions. You can still use the old |
|
||||||
function names by defining the \c FLTK_1_0_COMPAT symbol on |
|
||||||
the command-line when you compile (\c -DFLTK_1_0_COMPAT) or in |
|
||||||
your source, e.g.: |
|
||||||
|
|
||||||
\code |
|
||||||
#define FLTK_1_0_COMPAT |
|
||||||
#include <FL/Fl.H> |
|
||||||
#include <FL/Enumerations.H> |
|
||||||
#include <FL/filename.H> |
|
||||||
\endcode |
|
||||||
|
|
||||||
The following table shows the old and new function names: |
|
||||||
|
|
||||||
<CENTER> |
|
||||||
<TABLE WIDTH="80%" BORDER="1"> |
|
||||||
<TR> |
|
||||||
<TH>Old 1.0.x Name</TH> |
|
||||||
<TH>New 1.1.x Name</TH> |
|
||||||
</TR> |
|
||||||
<TR> |
|
||||||
<TD>contrast()</TD> |
|
||||||
<TD>fl_contrast()</TD> |
|
||||||
</TR> |
|
||||||
<TR> |
|
||||||
<TD>down()</TD> |
|
||||||
<TD>fl_down()</TD> |
|
||||||
</TR> |
|
||||||
<TR> |
|
||||||
<TD>filename_absolute()</TD> |
|
||||||
<TD>fl_filename_absolute()</TD> |
|
||||||
</TR> |
|
||||||
<TR> |
|
||||||
<TD>filename_expand()</TD> |
|
||||||
<TD>fl_filename_expand()</TD> |
|
||||||
</TR> |
|
||||||
<TR> |
|
||||||
<TD>filename_ext()</TD> |
|
||||||
<TD>fl_filename_ext()</TD> |
|
||||||
</TR> |
|
||||||
<TR> |
|
||||||
<TD>filename_isdir()</TD> |
|
||||||
<TD>fl_filename_isdir()</TD> |
|
||||||
</TR> |
|
||||||
<TR> |
|
||||||
<TD>filename_list()</TD> |
|
||||||
<TD>fl_filename_list()</TD> |
|
||||||
</TR> |
|
||||||
<TR> |
|
||||||
<TD>filename_match()</TD> |
|
||||||
<TD>fl_filename_match()</TD> |
|
||||||
</TR> |
|
||||||
<TR> |
|
||||||
<TD>filename_name()</TD> |
|
||||||
<TD>fl_filename_name()</TD> |
|
||||||
</TR> |
|
||||||
<TR> |
|
||||||
<TD>filename_relative()</TD> |
|
||||||
<TD>fl_filename_relative()</TD> |
|
||||||
</TR> |
|
||||||
<TR> |
|
||||||
<TD>filename_setext()</TD> |
|
||||||
<TD>fl_filename_setext()</TD> |
|
||||||
</TR> |
|
||||||
<TR> |
|
||||||
<TD>frame()</TD> |
|
||||||
<TD>fl_frame()</TD> |
|
||||||
</TR> |
|
||||||
<TR> |
|
||||||
<TD>inactive()</TD> |
|
||||||
<TD>fl_inactive()</TD> |
|
||||||
</TR> |
|
||||||
<TR> |
|
||||||
<TD>numericsort()</TD> |
|
||||||
<TD>fl_numericsort()</TD> |
|
||||||
</TR> |
|
||||||
</TABLE> |
|
||||||
</CENTER> |
|
||||||
|
|
||||||
\section migration_1_1_images Image Support |
|
||||||
|
|
||||||
Image support in FLTK has been significantly revamped in 1.1.x. |
|
||||||
The Fl_Image class is now a proper base class, with the core |
|
||||||
image drawing functionality in the Fl_Bitmap, Fl_Pixmap, and |
|
||||||
Fl_RGB_Image classes. |
|
||||||
|
|
||||||
BMP, GIF, JPEG, PNG, XBM, and XPM image files can now be |
|
||||||
loaded using the appropriate image classes, and the |
|
||||||
Fl_Shared_Image class can be used to cache images in memory. |
|
||||||
|
|
||||||
Image labels are no longer provided as an add-on label type. |
|
||||||
If you use the old \c label() methods on an image, the |
|
||||||
widget's \c image() method is called to set the image |
|
||||||
as the label. |
|
||||||
|
|
||||||
Image labels in menu items must still use the old labeltype |
|
||||||
mechanism to preserve source compatibility. |
|
||||||
|
|
||||||
\section migration_1_1_keyboard Keyboard Navigation |
|
||||||
|
|
||||||
FLTK 1.1.x now supports keyboard navigation and control with |
|
||||||
all widgets. To restore the old FLTK 1.0.x behavior so that only |
|
||||||
text widgets get keyboard focus, call the Fl::visible_focus() |
|
||||||
method to disable it: |
|
||||||
|
|
||||||
\code |
|
||||||
Fl::visible_focus(0); |
|
||||||
\endcode |
|
||||||
|
|
||||||
|
|
||||||
\htmlonly |
|
||||||
<hr> |
|
||||||
<table summary="navigation bar" width="100%" border="0"> |
|
||||||
<tr> |
|
||||||
<td width="45%" align="LEFT"> |
|
||||||
<a class="el" href="osissues.html"> |
|
||||||
[Prev] |
|
||||||
Operating System Issues |
|
||||||
</a> |
|
||||||
</td> |
|
||||||
<td width="10%" align="CENTER"> |
|
||||||
<a class="el" href="index.html">[Index]</a> |
|
||||||
</td> |
|
||||||
<td width="45%" align="RIGHT"> |
|
||||||
<a class="el" href="migration_1_3.html"> |
|
||||||
Migrating Code from FLTK 1.1 to 1.3 |
|
||||||
[Next] |
|
||||||
</a> |
|
||||||
</td> |
|
||||||
</tr> |
|
||||||
</table> |
|
||||||
\endhtmlonly |
|
||||||
|
|
||||||
*/ |
|
||||||
@ -1,80 +0,0 @@ |
|||||||
/** |
|
||||||
|
|
||||||
\page migration_1_3 Migrating Code from FLTK 1.1 to 1.3 |
|
||||||
|
|
||||||
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 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 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. |
|
||||||
|
|
||||||
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. |
|
||||||
|
|
||||||
|
|
||||||
\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> |
|
||||||
<table summary="navigation bar" width="100%" border="0"> |
|
||||||
<tr> |
|
||||||
<td width="45%" align="LEFT"> |
|
||||||
<a class="el" href="migration_1_1.html"> |
|
||||||
[Prev] |
|
||||||
Migrating Code from FLTK 1.0 to 1.1 |
|
||||||
</a> |
|
||||||
</td> |
|
||||||
<td width="10%" align="CENTER"> |
|
||||||
<a class="el" href="index.html">[Index]</a> |
|
||||||
</td> |
|
||||||
<td width="45%" align="RIGHT"> |
|
||||||
<a class="el" href="development.html"> |
|
||||||
Developer Information |
|
||||||
[Next] |
|
||||||
</a> |
|
||||||
</td> |
|
||||||
</tr> |
|
||||||
</table> |
|
||||||
\endhtmlonly |
|
||||||
|
|
||||||
*/ |
|
||||||
@ -0,0 +1,52 @@ |
|||||||
|
/** |
||||||
|
|
||||||
|
\page migration_1_4 Migrating Code from FLTK 1.3 to 1.4 |
||||||
|
|
||||||
|
This appendix describes the differences between the FLTK |
||||||
|
1.3.x and FLTK 1.4.x functions and classes. |
||||||
|
|
||||||
|
\section migration_1_4_old_versions Migrating From FLTK 1.0 Or 1.1 To 1.4 |
||||||
|
|
||||||
|
If you want to migrate your code from FLTK 1.0 or 1.1 to FLTK 1.4, |
||||||
|
then you should first consult the relevant appendices in FLTK 1.3 |
||||||
|
documentation online or by downloading the FLTK 1.3 documentation. |
||||||
|
See https://www.fltk.org/doc-1.3/index.html |
||||||
|
and/or https://www.fltk.org/software.php , respectively. |
||||||
|
|
||||||
|
|
||||||
|
\section migration_1_4_headers Minor Changes in Header Files |
||||||
|
|
||||||
|
(to be documented) |
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
\section migration_1_4_preferences Fl_Preferences |
||||||
|
|
||||||
|
(to be documented) |
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
\htmlonly |
||||||
|
<hr> |
||||||
|
<table summary="navigation bar" width="100%" border="0"> |
||||||
|
<tr> |
||||||
|
<td width="45%" align="LEFT"> |
||||||
|
<a class="el" href="osissues.html"> |
||||||
|
[Prev] |
||||||
|
Operating System Issues |
||||||
|
</a> |
||||||
|
</td> |
||||||
|
<td width="10%" align="CENTER"> |
||||||
|
<a class="el" href="index.html">[Index]</a> |
||||||
|
</td> |
||||||
|
<td width="45%" align="RIGHT"> |
||||||
|
<a class="el" href="development.html"> |
||||||
|
Developer Information |
||||||
|
[Next] |
||||||
|
</a> |
||||||
|
</td> |
||||||
|
</tr> |
||||||
|
</table> |
||||||
|
\endhtmlonly |
||||||
|
|
||||||
|
*/ |
||||||
Loading…
Reference in new issue