> MacArthur, Ian (SELEX GALILEO, UK) wrote:
>
> > Anyway, what I was going to suggest is that Fl::get_system_colors()
> > could maybe be extended to cover setting the xclass, to cover those
> > cases where show() is called "wrongly" at initialisation.
> >
> > Would that help at all?
>
> Or something like Fl::set_window_class("MyWindowClassName") before
> calling show for the first time ?
>
> Albrecht
Or something as Fl_Window::set_class(myClassName) would be IMHO even better in
that case.
We should be careful from now not to multiplicate (pseudo) global functions in
Fl when there is not a good reason to do it.
This class is really too populated ...
In my cairo addon, I created a state class to limit the number of attributes
and methods addons, also, I named the functions as Bill suggested first, but
now I wonder if I should not move my static functions to Fl_Window too as the
cairo addon granularity is the Window anyway.
Fabien
_______________________________________________
fltk-dev mailing list
[email protected]
http://lists.easysw.com/mailman/listinfo/fltk-dev
