Fabien Costantini wrote:
>> Alvin wrote:
>>> I just need to figure out how to determine if the window is already
>>> maximised :) Oh, and how to "restore" the window as well.
> ./..
>> Maybe someone on the core can accumulate all of these X11 and Windows
>> examples and roll it all up into the FLTK API, eg:
>>
>> Fl_Window::maximize()
>> Fl_Window::minimize()
>> Fl_Window::normalize()
>> Fl_Window::ismaximized()
>> Fl_Window::isminimized()
>> Fl_Window::isnormalized()
>>
>> ..might be a nice way to do it.
>>
>> Certainly this seems to come up a lot.
> I agree and also thought about this set of functionality more than once,
> 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,
and don't actually get coded and added to the docs until later.
This way adding the code later won't break the established 1.3.0 ABI
_______________________________________________
fltk mailing list
[email protected]
http://lists.easysw.com/mailman/listinfo/fltk
