FLTK mostly uses "xyz(value)" to set, and "xyz()" to get.
The set_xyz() and clear_xyz() are used instead of xyz(true) and xyz(false). However I feel that in most or all cases this was a mistake. The xyz(bool) should have been provided as the only set api. I like adding the "ed" when it makes syntatic sense for the get, so "maximized(bool)" would be how you set it, and "maximized()" is how you read it. The idea of using a set of bits to control all the window settings with one call may be pretty good. It appears that on many OS's that is what you have to do underneath anyway. Greg Ercolano wrote: > I don't think the FLTK coding standards cover the issue of naming > new methods regarding 'setting' vs. 'getting'. _______________________________________________ fltk-dev mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-dev
