On Thu, Jul 22, 2004 at 01:59:05PM -0400, george young wrote:
> In fact it seems that the second and third args, "expand" and "fill",
> respectively, must both be True (the default) for the scrolledwindow
> to function usefully:
[...]
> Maybe this is obvious to those with a deep grasp of Box packing semantics,
> but it certainly took me a while to figure out...
>
> Perhaps this should be a FAQ? Or is it really too obvious?
I'm not sure. It's certainly obvious to someone with some glade
experience -- I'm repeating myself here, but using glade is really a
good way to learn how container expansion and fill behave.
I added a FAQ a while back at Dan's request which resembles closely a
message I sent to the list a while back; it ends in the phrase
in reality fill, expansion, requested sizes, widget expansion
semantics, container packing semantics, electron spins and lunar
cycles are computed to determine how much space each widget wins.
What you've discovered is something related to widget expansion
semantics: if not configured to expand in its parent container, a
ScrolledWindow will take up very little space (mainly because being
scrollable it is not bound to a specific dimension and because of that
is biased to lose the war for space in its container).
If you think that's worth adding to the FAQ, by all means do :-)
Take care,
--
Christian Robottom Reis | http://async.com.br/~kiko/ | [+55 16] 3361 2331
_______________________________________________
pygtk mailing list [EMAIL PROTECTED]
http://www.daa.com.au/mailman/listinfo/pygtk
Read the PyGTK FAQ: http://www.async.com.br/faq/pygtk/
