When writing comments, FLuid would check if the comment was
C compatible. However, comments don;t need to comply to C
syntax. We could check for the "*/", but is that really needed?
This commit adds a cairo_surface flush after calling the draw callback.
This fixes the test/cairo_test demo program under Windows.
At least under Windows the Cairo callback used in Fl_Cairo_Window
didn't draw anything with current Windows 10, MinGW (32-bit) and
Cairo 1.15.12 for Windows. It worked well under Linux though. Anyway,
the flush should do no harm.
Loading GIF images could crash if there was no "Global Color Table"
but individual "Local Color Tables" with individual images.
Now local color tables are used correctly if available, but images that
lack both global and local color tables are being loaded with a default
(gray) color table and a warning is issued with Fl::warning().
The default color table uses black and white in the first two indices
as recommended by the standard.
Cherry-picked from: 35e03733f4
This is intentionally committed to the 'master' branch although it is
currently only useful for FLTK 1.3.x ABI checks.
In the future we will need it for FLTK 1.4.x or higher.
Generating driver documentation can now be configured with CMake. The new
configuration OPTION_INCLUDE_DRIVER_DOCUMENTATION is "marked as advanced"
since only advanced users and/or FLTK developers need this.
Previously this could only be achieved by editing documentation/Doxyfile.in.
Added missing documentation option descriptions as well.
Note: current mail notifications are configured for first tests.
We may need to reconfigure this later.
See build logs at https://travis-ci.com/fltk/fltk
This implementation differs from existing fltk-test and also gitlab implementation :
- minimum, fast light implementation: stripoped all unused constructions compared to other implementations
- supports successful builds of four targets (linu, osx and then gcc and clang for each of them)
- uses before_script instead of before_install
- uses after_success for building documentation, instead of building always if error
- only builds documentation on linux targets for now (can easily change if future)
