| |
| |
On 4/7/22 15:03 Manolo wrote:
I have renamed the option which is now OPTION_USE_CAIRO
and tried to improve the description of Cairo-related options.
This leaves us with 3 cairo-related options :
OPTION_CAIRO add support for Fl_Cairo_Window
OPTION_CAIROEXT use FLTK code instrumentation for
Cairo extended use
OPTION_USE_CAIRO all drawing to X11 windows uses Cairo
Since OPTION_CAIRO is really nothing but opening support
for class Fl_Cairo_Window, I would propose to rename it
OPTION_FL_CAIRO_WINDOW. OPTION_CAIROEXT could become
OPTION_FL_CAIRO_WINDOW_EXT.
This would hopefully improve understanding the difference
between the options.
Comments ?
-1: Please don't do this.
We should leave the old option names as is for backwards
compatibility with long standing FLTK 1.3 projects. These names also
correspond to similarly named configure options '--enable-cairo' and
'--enable-cairoext'. If we changed these names all users
(developers) relying on the old names would have to change their
build systems.
The explanatory text may be changed but it's important to improve
the documentation (currently in README.Cairo.txt only ?) to make
clear what these options are doing.
OPTION_CAIRO ('--enable-cairo') is probably the most used option of
these two options (if any). We have working examples for this.
OPTION_CAIROEXT ('--enable-cairoext') is probably less known and
much less used and thus less important. I believe we don't have
example code for this anyway. Maybe nobody uses it.
--
You received this message because you are subscribed to the Google Groups "fltk.coredev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to fltkcoredev+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/fltkcoredev/158cb02f-668d-a9a0-8e6d-88d0501a8fd1%40online.de.
[ Direct Link to Message ] | |
|
| |
