> Thing is, if you were making a program where you could drag
> one physical window into another so that it 'snaps in' becoming
> a subwindow, one would think this re-parenting could be done with
> Fl_Window::add() (which is what the first example is trying to show
> I think), but it might be different because FLTK's event loop hasn't
> been called yet, so the behavior might be different than during
> a construction.
After reading back my above paragraph /after/ having my morning coffee,
I see that last part seems kinda unclear.
What I meant to stress is that one should likely be watchful
for differences in the behavior of a given sequence of FLTK window
creation commands when used before vs. after the FLTK event loop
has been called. (ie. during setup vs. after the program has been
running a while, such as the 'snap in' example I was describing)
The reason being that since FLTK doesn't create the physical windows
until after the FLTK event loop has gotten some cpu, there's surely
differences internally with FLTK for those two situations, so behaviors
might be different in those cases for methods like Fl_Window::add().
I'm not sure there are differences, it's just that I'd be watchful
for them.
_______________________________________________
fltk mailing list
[email protected]
http://lists.easysw.com/mailman/listinfo/fltk
