>
> Though it probably just means there's a missing end()
> somewhere.
No, it's structural:
class Calendar : public Fl_Window { ... }
class DateInput : public Fl_Group {
static Calendar* cal;
public: Calendar() {
// new components
end()
// initialize cal if cal == 0
// oops, I didn't want a subwindow
}
}
int main() {
Fl_Window w = new Fl_Window(..)
new DateInput(...);
end();
...
}
Where's the missing end() ?
>
> When I derive widgets from Fl_Group or Fl_Window
> that are 'completely defined' by the constructor
> (like the calendar widget), I usually put the end()
> in the group's constructor, ...
> I don't think of the begin()/end() stuff as evil,
> as long as it's understood how it works. ...
Look, there are lots of things about fltk that I like, but this
isn't one of them. Relying on global state is evil; we all
learned that in computer science 101.
Cheers, and thanks again,
Stan
_______________________________________________
fltk mailing list
[email protected]
http://lists.easysw.com/mailman/listinfo/fltk
