Further extended GTK code survey to clarify the role of the minimum_size, it is indeed ignored by most standard containers, but it is actually used by Gtk::Layout as starting point for the query sequence. Thus it does not make sense to treat minimum and natural size differently; both queries should be responded by returning our size constraint. Unless we define additional borders and margins in the CSS, we can be sure that GTK will base the size allocation on the exact values returned from the get_required_* functions. These functions will be invoked only from within the Event Loop and after the ctor is finished, but before the first "draw". They will be re-invoked on each "size change" event and on each focus change (since a focus change may change the style and thus the actual extension). |
||
|---|---|---|
| .. | ||
| gtk | ||
| c++11.txt | ||
| codingGuidelines.txt | ||
| darkCorners.txt | ||
| index.txt | ||
| linkingStructure.txt | ||