>
>
> > or should it be window->is_maximum_size()
Or we just change this boolean (quite limited) approach and use instead:

virtual void show_mode(int  showmode);
int show_mode() const;

Here the functiuonality is different, operations of maximisation and 
inconization(minimization) and possibly future others could be achieved with 2 
simple api, as I suggested in the RFC I opened concerning these functions.

BTW, I also share the opinion that :
  - most get/set api in fltk1 have the same name even if they are exceptions
  - set_xxx also means already something for bit masking manip.

Fabien
_______________________________________________
fltk-dev mailing list
[email protected]
http://lists.easysw.com/mailman/listinfo/fltk-dev

Reply via email to