On Jan 11, 2011, at 1:21 AM, MacArthur, Ian (SELEX GALILEO, UK) wrote:
>
>> 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?
+1 for making the Fl_X class private (and not API for developers...)
________________________________________
Michael Sweet, Easy Software Products
_______________________________________________
fltk-dev mailing list
[email protected]
http://lists.easysw.com/mailman/listinfo/fltk-dev
