On 15 Jun 2008, at 17:18, Jane wrote: >> > Whow! Indeed impressive ^^) > It helps, thank you Ian.
Thanks! You're welcome. It was a bit of fun to do, and it took me back to my days doing analogue synth design - hence the old skool adsr envelope generators! Actually, I'd have really liked to have an adsr plot back then... > 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 ^^) Yes - I was trying to keep it simple, so grouping the controls into a derived class, and having an ID per class instance was easier than giving every controller a unique ID. > 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). Yes - that's the basic idea. Note that this is not really "good" C++ though, the purists would take issue with a lot of it. But you said you were coming from a C background, so I was going for a "mostly-C" coding style, while still getting some of the benefits. Also, the array of widgets really ought to be in some sort of list, I'd suggest. The C++ STL provides several ways of doing this that are more powerful (although not faster) than a simple array - but perhaps at the cost of some clarity for a C-programmer. Stan seems to be good at that sort of thing, if you get stuck! Cheers, -- Ian _______________________________________________ fltk mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk
