> > For the moment, if a user wants colours, etc, one can always revert the
> > style.
>
> How? As an only occasional FLTK 2 user I don't know how to do that.
>
Above main, declare "bool mytheme() { fltk::reset_theme(); }", then as the
first line of main add "theme(mytheme);".
FLTK will work the rest out from there. You can probably call reset_theme()
somewhere else in the code, but then you'd also have to call reload_theme() and
make sure you had called flush() before that.
> > I do intend to add proper transparency to the images as some point,
> > as well as segregation the #includes amongst other things, but I really
> > only forced the XP theme to be the default in an effort to get some
> > feedback.
>
> Hmm, very little feedback so far, AFAICT. Maybe there are not so many
> users that update their FLTK 2 versions frequently...
>
Little?! Where! :-P
Yeah, there have been surprisingly fewer than I expected.....
> But, please take care that such incompatible changes don't make more
> users drop FLTK, because they say "Hey, what are they doing? Now they
> broke my working software (again)." Rumors say that many FLTK2 users
> went away from FLTK2 because of lots of incompatible changes in the
> past.
In my head, it worked as so:
Make the theme the default for 2 or 3 weeks. I'd then get feedback and fix what
needed to be fixed, and then move the xp theme from the default (fltk_theme())
to it's own xp_theme(), where a user could then call theme(xp_theme) at the top
of their main function. I'll revert it in the near future, in any case, and
provide it as a xp_theme().
Obviously, I need far more forethought next time!
Ben
_______________________________________________
fltk-bugs mailing list
[email protected]
http://lists.easysw.com/mailman/listinfo/fltk-bugs
