This is a brilliant idea. I've not thought about doing it that way before. This also saves me writing code in fluid, which I really don't like.
Thanks, Oguz > What you can also do is reduce the amount of code that you provide > in the fluid generated part to a minimum. Either provide the callback > code in a separate file, like in the documentation for fluid, or > create a very thin base class in fluid with virtual callbacks. > Then [using a more standard code editor than fluid] override these > callbacks and provide the implementation logic in a derived class. > > I think I have a simple example at home I can post this evening. > > D. > _______________________________________________ fltk mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk
