On 28.03.2009, at 00:55, imacarthur wrote: >> 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. > > Yup. +1. > > And sometime in the future, 1.x.y, Fl_Browser_::scrollbar_width() > will go away and everything will be consistent and lovely...
+1 ---- http://robowerk.com/ _______________________________________________ fltk-dev mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-dev
