Richard Penman wrote:
>> Greg Ercolano schrieb:
>>> But most everyone uses the begin/end stuff in fltk;
>>> it works well, and I've never seen it be a problem.
>> Imho a newbie runs into problems with this nearly 100%. As soon as you
>> start to write your own composite widgets without Fluid you will hit
>> this problem, sooner or later. And it is really serious. Forgetting the
>> end() leads to mysterious behaviour of the application. When I had this
>> problem in the beginning it took me hours if not days to find the cause.
>
> I've been using Fluid up to now and just went through the same experience!
I'd suggest this is a documentation problem then.
I remember when I first started using FLTK, this begin()/end()
thing was mentioned right up front in the docs I was reading.
The very first example of fltk code (hello world) showed the
begin()/end() thing, and I remember the docs below it saying
what that was. It made perfect sense too, because otherwise
you'd have to explicitly 'add' every new widget to its parent
to define the parenting order, which is what makes most GUI
code ugly/redundant.
Since I'm no longer a newbie, I don't know where it is that
people first jump into FLTK documentation. With me it started
with a printed manual (I think I still have it) back in the 1.0 days.
It would be good if you both could say where you started reading
docs to begin learning FLTK, and tell the folks managing those docs
to mention/clarify the begin()/end() stuff in the very first examples.
_______________________________________________
fltk mailing list
[email protected]
http://lists.easysw.com/mailman/listinfo/fltk
