From: Daniel Boles Date: Tue, 12 Sep 2017 21:48:58 +0000 (+0100) Subject: FlowBox: Explain how to avoid inflated min size X-Git-Tag: archive/raspbian/3.24.39-1+rpi1~1^2~65^2~39^2~178 X-Git-Url: https://dgit.raspbian.org/?a=commitdiff_plain;h=26104a30a582f62086c6a5410d2aaee6a4c3ff7f;p=gtk%2B3.0.git FlowBox: Explain how to avoid inflated min size along the orthogonal orientation. It seems a FlowBox on its own can only handle being shrunk along its main orientation. The orthogonal requests a huge min size – reserving what it would need if the main orientation got its min size, which would flow all children in 1 line orthogonally. Adding it to a ScrolledWindow (any policy) enables free shrinking, so size_allocate() can reflow how users in this situation probably expect. https://bugzilla.gnome.org/show_bug.cgi?id=787021 --- diff --git a/gtk/gtkflowbox.c b/gtk/gtkflowbox.c index e9e2504fd0..3f204b9a57 100644 --- a/gtk/gtkflowbox.c +++ b/gtk/gtkflowbox.c @@ -41,6 +41,10 @@ * Reducing the height will require more columns, so a larger width will * be requested. * + * The size request of a GtkFlowBox alone may not be what you expect; if you + * need to be able to shrink it along both axes and dynamically reflow its + * children, you may have to wrap it in a #GtkScrolledWindow to enable that. + * * The children of a GtkFlowBox can be dynamically sorted and filtered. * * Although a GtkFlowBox must have only #GtkFlowBoxChild children,