It is a good idea. But does this break the license of fltk? What should I do to fit the license? Only need make the source code of MyFl_** availabe to public or the whole application based on "MyFl_**". I hope the application can be linked to fltk statically. Thanks.
> Sparkaround wrote: > > And Fl_Text_Display use fl_rectf so that I can't set background image for > > it without rewriting plenty of draw methods. And it will be a difficutl to > > update these draw methods if fltk updated. > > I suppose you could grab a 'snapshot' of the fltk widget in question > (just the .cxx and .H file for the widget in question), > and make it part of your code base, renaming it to something like > MyFl_Text_Display, then hack the draw() code as you like. > > This way even if FLTK updates, your version of the widget remains > constant, and you don't have to worry about FLTK updates as much, > since the public interfaces usually remain consistent. > > It sure beats hacking FLTK directly, as then it becomes very > hard to update FLTK, as you have to 'merge' all your customizations > every release, and that leads to madness. _______________________________________________ fltk mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk
