> > OK, the ftp server seems to have come back on line. Eventually. > > Here's the "full" version of the demo I tried to post before - > there's still not that much to it, mind you. > > http://www.imm.uklinux.net/fltk/anim_demo.tgz > > Anyway, it's all coded in a very C-style (the OP indicated a > preference for C, and that suits me too...!) > For example, the lists of widgets are held in simple arrays (they > really ought to be help in a proper list or other suitable STL > container, of course, in the C++ style.) > The casts (such as they are) are C-style casts, etc. Use of printf > rather than messing about with streams. > And so on... > > Anyway, the demo attempts to show: > - Using fluid to create your own composite widget classes > - Using those widget classes > - Making your own widget class "by hand" (derived from Fl_Box) > - Referencing the "home made" class in fluid > - Using timers > - Using callbacks > - Laying out widgets programatically > - Updating widgets programatically > - Basic drawing (lines, colours) > > Hope it's some help. I had fun anyway! > > Cheers, > -- > Ian > > >
Whow! Indeed impressive ^^) It helps, thank you Ian. So, you did some Fl_Groups (for a mixer strip and adsr) and use them as widgets. Right? I can see how you added a ID for each group. But this way only a group has an ID, not the single controller. I need to tweak it a bit but its almost directly usable in my application ^^) Very cool, now i can use FLUID to create my UI, because now i know how it can be done! I even understand the usefullnes of classes here (eg, create one mixer strip as group, add this group like adding a widget, repeat if you need more of this). Awesome. Thank you again! Jan _______________________________________________ fltk mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk
