> I also believe that we already had a similar problem. This one can
> be fixed easily with "friend class Fl_X;" in Fl_Widget.H, like this
> patch:
>
> Index: FL/Fl_Widget.H
> ===================================================================
> --- FL/Fl_Widget.H (revision 9300)
> +++ FL/Fl_Widget.H (working copy)
> @@ -99,6 +99,7 @@
> */
> class FL_EXPORT Fl_Widget {
> friend class Fl_Group;
> + friend class Fl_X;
>
> Fl_Group* parent_;
> Fl_Callback* callback_;
>
>
> ... instead of making the enum public. I'm not sure which one is
> better though, but I'd tend to use the friend statement in this
> case. Anybody?
Yes - I like the look of that better, and it should have the desired effect.
> First, I'm not sure at all that adding static class members keep
> the ABI intact, as Manolo states in the comments to the offending
> code. This should probably be in fltk.development, but anyway...
> Manolo, did you really intend to add static class members as opposed
> to static external variables in the ABI compatible case? ...
Oh, that's a point. That hadn't occurred to me but yes, that will add static
class members in the "backwards compatible" case. I wonder if that's really
what we'd want? Would that mean that all wondows get "the same" x,y,w,h values
then...? Hmm...
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 mailing list
[email protected]
http://lists.easysw.com/mailman/listinfo/fltk
