On 15 Oct 2011, at 04:44, David wrote: > Okay, I see that's actually a variable and not a #define, ALL_CAPS threw me, > so that takes care of that.
Yup - throws me too, every time. And I assume everyone else... I guess it is historical - maybe it really was a define once upon a time. I think it would be easy enough to make it lowercase now, but keep an uppercase #define around that referred to the "new" lowercase name for backwards compatability. Or something... Though just having that floating around in global scope seems a little untidy - maybe a method could be added to FL (or maybe to Fl_Widget?) to set the "global" size in a more managed way. > What I'm after is to reduce duplication and ease use of the frame work by > apps while having widgets function in an intuitive way. The changes I made > fixed the way check list boxes work (or browsers for fltk) and supported all > existing features of the list boxes. OK > It also fixed the input widgets to handle limiting input with a simple > paramter setting (part was already there but needed to be expanded to other > controls and fix so users setting values are also limited and combo boxes > selections from being too long). Hmm, yes, But I think the way it is at present is (more or less) by design - it is intended that users set their own widget handling explicitly. And if you need to make a lot of widgets that all have the same handling, it is trivial to make a subclass that does that. _______________________________________________ fltk mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk
