> Fabien Costantini wrote: ./.. > > so I believe we are quite numerous in favor of such an addon. > > We have some priority work to do with utf8 but I promise I would care for > > that one if it's in qn RFE somewhere in the 1,3 roadmap ;-) > > Yes, I agree get 1.3 solid first. > > Though it might make ABI issues easier as the 1.3.x path evolves > if these methods are included as 'stubs' that just return() for now,
True, but then it should be more analyzed :-) As an example, it is probably better to further instead of void maximize() a maybe a bit richer form like: void maximize(bool on_off) to use it for maximize and un-maximize ops. This way we would only have 4 get/set methods to maintain. We should maybe also think about the mac platform and the possibility for the developer to provide 'smart' maximize operations, so probably it could be interesting to provide them as virtual methods ... Going a bit deeper in the analysis, then we could also consider adding new fl events (i.e: FL_MAXIMIZE, FL_MINIMIZE) and these methods would rely on/use them, so that that we could also handle them in a custom handle() method. Fabien _______________________________________________ fltk mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk
