> I just updated to the head of 1.3, and my app failed to compile,
> complaining that Fl_X was undefined. Looking at FL/mac.H, it looks
> like it's intentionally hidden when compiling against an application.
> Hiding system specific stuff seems like a good idea, but it looks like
> this is inconsistent with X11 and win32. And if Fl_X is meant to be
> hidden, documentation should be removed for it, and there should be
> some alternate way to write:
>
> int has_windows() { return Fl_X::first != NULL; }
>
> 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.
What do folk think?
I don't know - I'd guess not, for "safety" reasons, but there are some
advantages, too...
SELEX Galileo Ltd
Registered Office: Sigma House, Christopher Martin Road, Basildon, Essex SS14
3EL
A company registered in England & Wales. Company no. 02426132
********************************************************************
This email and any attachments are confidential to the intended
recipient and may also be privileged. If you are not the intended
recipient please delete it from your system and notify the sender.
You should not copy it or use it for any purpose nor disclose or
distribute its contents to any other person.
********************************************************************
_______________________________________________
fltk-dev mailing list
[email protected]
http://lists.easysw.com/mailman/listinfo/fltk-dev
