>
> On 13 Jun 2008, at 20:53, [EMAIL PROTECTED] wrote:
>
> >> Then your set_widget(130, 50); would perhaps become something like...
> >>
> >> set_widget(int id, float val) {
> >> widget_array[id]->value(val);
> >> }
> >
> > But Fl_Widget doesn't have a value() method. Keeping an array of
> > Fl_Valuator* might work, but might get messy because it's value()
> > is non-virtual; you'd have to research whether or not the base class
> > value() does what you want in all cases. Unfortunately fltk
> > doesn't do polymorphism very well.
>
> Yes, fair point Stan.
> It (the pseudo code) was more conceptual than practical.
> I guess for a synth system all the valuator widgets would have
> essentially similar value methods however, so picking an appropriate
> base class could work? Dunno...
>
And it's conceptually spot on of course. I'd just be concerned that
there would be some 'gotchas' trying to use non-virtual methods
through the pointer to base.
Best,
Stan
_______________________________________________
fltk mailing list
[email protected]
http://lists.easysw.com/mailman/listinfo/fltk
