On Thursday, February 18, 2021 at 1:52:08 PM UTC+1 Albrecht Schlosser wrote:
All (not only devs),
in another post I wrote:
> Generally I *believe* ...that all these
> FL_CFG_GFX_* definitions should not be necessary and
> *maybe* the entire [file] 'config_lib.h' could be
> removed. ... But that's something that needs some
> time for investigation...
…
Today I removed the remaining references of config_lib.h except those in
src/Fl.cxx which are still needed to implement the static assignment of
runtime configuration variables (documented here):
https://www.fltk.org/doc-1.4/group__cfg__gfx.html
https://www.fltk.org/doc-1.4/group__cfg__prn.html
https://www.fltk.org/doc-1.4/group__cfg__win.html
https://www.fltk.org/doc-1.4/group__cfg__sys.html
…
As always, all comments and suggestions would be very much appreciated. TIA.
Question 1: keep these runtime features?
I'm not completely sure but my impression is that until FLTK can support a build in which
these global variables (or function results) can take distinct values according to the
application's running context, these variables/functions are not useful. They may even give to FLTK
users a false impression that FLTK supports alternative graphics or printing systems.
One expressive situation is under macOS, where FLTK can be built to use either the Quartz
or X11 drawing systems. Any FLTK app uses either one or the other in a invariable way.
Another case arises with the proposed GDI+ branch. There, either GDI+ or GDI is used,
and there's no way for an app to choose between them at run-time.
Question 2: turn them into functions?
N/A
