> > > 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. >
Not that easy when new to a framework. Saying, let the max input size be 32 (and it's always that, for keyboard input or setting a value, or in the combo box even if the list box item is too large) is much easier than having to study how to write a handler. The amount of code was so small and offers a common desired result that I would argue that it should be added. _______________________________________________ fltk mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk
