> 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 understand and use all of it ;-) > > So, what to do now? Revert? Rewrite/remove this documentation chapter? > What about those who used this information in their programs?
Well, I'm not sure I understand all the in's and out's of this, so feel free to ignore my input... If I understood what Manolo was trying to do, he was only hiding Fl_X if FL_LIBRARY was not defined. The intent being to hide the low-level stuff from regular users... So, looking at that the other way, if someone needs to derive their own class from Fl_X in this way, then setting FL_LIBRARY may still allow them to do so, and they are likely to be getting into low-level stuff anyway so hiding it would be unnecessary... Is that the case? If so, we maybe need to update the docs to mention that, but the actual code change may be fine? Interestingly, the code comments in FL/x.H also include this little gem: // Warning: this object is highly subject to change! It's definition // is only here so that fl_xid can be declared inline: Which, given the recent change is no longer true, so maybe the comments need to be updated to reflect the new way of doing things, maybe even mention the effect of FL_LIBRARY now? 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
