>
>
> > void DataGenerator::StartCB_i(Fl_Widget* wgt, void* v)
> > {
> > Fl_Button* button =3D (Fl_Button*)w;
>
>
> Having created this "button" widget, it might be more portable to use it
> in subsequent refs, rather than calling startBtn explicitly?
> Perhaps that is what you intended?
>
> > if(state)
> > {
> > state =3D false;
> > if(startBtn->label() =3D=3D "Continue")
> > {
> > startBtn->label("Stop");
>
>
> > Have i over egged the pudding here? Is there a more=20
> > recommended or 'safer' solution?
>
> I didn't try to compile the code, but it looks OK I think. This is
> probably as good a way as any other to get to the correct callback
> method, so should be fine.
> I assume you tested this and it worked OK for you?
>
> Though I would always derive my "outer" widgets from fltk widgets, if it
> were me...
>
thanks, yes it all tested and runs fine, not a bug in sight, one reason is i am
making judicious use of the deactivate call haha so it makes the logic a lot
easier by definition, it is also appropriate as the GUI only serves to set the
aformentioned algorithm in motion,or stop it and do a new setup, other buttons
can be used to open other program features, but they have their own windows.
As far as the 'outer widget' goes, how exactly do you mean there?
_______________________________________________
fltk mailing list
[email protected]
http://lists.easysw.com/mailman/listinfo/fltk
