> > > I'm using fltk2-6844. I had created a class that is derived > > from fltk::Button. This class should store additional type > > information in Widget::type() as described in the docs: > > "Widget subclasses may store values in the range 0-99 here > > (larger values are reserved for use by FLTK)". But when I > > store and value in this area the button works always as a > > toggle button. > > Docs notwithstanding, I would advise against using the type to store any > additional information. I suspect that the fltk-2 code is "fragile" in > this respect, and am not all that sure about the fltk-1.x code either... > > If you are making your own subclass anyway, just add some private data > (or even public!) to your class to store the extra info. there and leave > the type mechanism alone.
Of course you're right, but I had the problem, that I create a special group class where the children can be attached to any border or corner. Because I don't want to store this attach information in the group itself, I tried to store this attach information by the child. Because the group can contain any widget, I need a base class storage. I know this is not very object-oriented like. > > Also note that fltk-2 is not actively maintained, so it is unlikely ever > to be "fixed". You might be better off with fltk-1.1 or fltk-1.3. > Does that mean fltk-2 will be no longer developed? I'm using fltk-e because I think that the API is much better than fltk-1.1. _______________________________________________ fltk mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk
