> Greg Ercolano wrote: ./.. > > Should we document Fl_Browser_::scrollbar_width() as being deprecated, > > and make a new Fl_Browser_::scrollbar_size() instead, to be consistent > > with the global's existing naming? > > Hmm, and if we do that, there's the added benefit where the old > Fl_Browser_::scrollbar_width() call could still do the existing behavior > of basically changing the global Fl::scrollbar_size(), and the new > Fl_Browser::scrollbar_size() could have the new 'per widget' control > that most folks would want/expect. > > In this way old programs would still work the way they did, without > modification, even if they depended on the 'global' behavior of the > local browser's scrollbar_width(). > > Would kinda kill two birds with one stone; deprecating the call and > the bad behavior, while introducing new/good behavior with a new call > that is more consistent naming-wise with the global. +1 for adding this new per widget API. +1 for making scrollbar_width() a macro that aliases scrollbar_default_size() to explicit the non per-widget (but still also interesting) behavior, and then deprecate scrollbar_width(). Fabien
_______________________________________________ fltk-dev mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-dev
