I voted for hiding as well, and Manolo did it recently for X11, but
now I found out that we *have* some documentation for Fl_X in the
chapter Operating System Issues, section Using a Subclass of
Fl_Window for Special X Stuff. This is X11 only, and I guess only
hardcore X11 developers can
I just noticed that there's a README in the test folder of fltk-1.3 in
svn.
I guess it's always been there and I never spotted it before.
I mention this only because it was last updated in Oct 1998, and
mentions some old stuff (such as the shiny demo) that are no longer
supported...
I guess we
On 13.01.2011, at 18:41, MacArthur, Ian (SELEX GALILEO, UK) wrote:
I just noticed that there's a README in the test folder of fltk-1.3 in
svn.
I guess it's always been there and I never spotted it before.
I mention this only because it was last updated in Oct 1998, and
mentions some old
On Jan 13, 2011, at 2:11 AM, Albrecht Schlosser wrote:
On 11.01.2011 17:32, Michael Sweet wrote:
Otherwise, hiding Fl_X for the mac is probably an oversight
and should be fixed.
One for Manolo I guess. Though... There is the bigger question of
whether Fl_X should be exposed or not.
On 13.01.2011 21:40, Michael Sweet wrote:
Document the workaround (define FL_LIBRARY) and note that such code will
likely not be portable to future versions of FLTK.
That's a good idea, and I believe such a warning is in the docs anyway,
so we can surely go that route. OTOH, FL_LIBRARY is
I voted for hiding as well, and Manolo did it recently for X11, but
now I found out that we *have* some documentation for Fl_X in the
chapter Operating System Issues, section Using a Subclass of
Fl_Window for Special X Stuff. This is X11 only, and I guess only
hardcore X11 developers can
