Stan wrote:
>> This is how I visualize it:
>> [..]
> That's a nice mental model, thanks. Unfortunately, actual
> behavior doesn't seem to match it. At least not to me :)
> For instance, look at this little demo. I'd have thought
> that after moving the boxes apart in the program (without
> taking a new snapshot) resizing the window would be based
> on the prior coordinates. But that doesn't seem to be the
> case. Am I missing something?
In this case the modifications are being made before
the windows have been physically constructed.
FLTK won't actually construct and display the widgets until
Fl::run() gets some cpu.
I imagine it would make a difference if you added a button,
and had the button's callback move the widgets around.
This would ensure your repositioning code was called after
Fl::run() got some cpu.
_______________________________________________
fltk mailing list
[email protected]
http://lists.easysw.com/mailman/listinfo/fltk
