On 11.01.2011, at 10:21, MacArthur, Ian (SELEX GALILEO, UK) wrote: > 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...
This is bad. The xid should be available to the user. In the original code, including any header except "FL/x.H" would not load (or "try not to load") anything specific to the underlying OS. However including "FL/x.H" (and *NOT* "FL/mac.H" or "FL/win32.H", these are included automatically when using x.H!) would open up access to the system resources. first_window, btw., is a static member of Fl_Window in FLTK2 (or rather fltk::Window). I find that a good idea. _______________________________________________ fltk-dev mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-dev
