Stretch, Shrink, and Collapse

By default, each column will be sized according to the “natural” size of the widest widget in that column (taking spanned columns into account). Sometimes, though, that does not work out very well, and you need more control over column behavior.

You can place an property on the . The value should be a single column number (again, 0‑based) or a comma‑delimited list of column numbers. Those columns will be stretched to take up any available space on the row. This helps if your content is narrower than the available space.

Conversely, you can place an property on the . Again, this should be a single column number or a comma‑delimited list of column numbers. The columns listed in this property will try to word‑wrap their contents to reduce the effective width of the column; by default, widgets are not word‑wrapped. This helps if you have columns with potentially wordy content that might cause some columns to be pushed off the right side of the screen.

You can also leverage an property on the , again with a column number or a comma‑delimited list of column numbers. These columns will start out “collapsed,” meaning they will be part of the table information but will be invisible. Programmatically, you can collapse and un‑collapse columns by calling on the . You might use this to allow users to control which columns are of importance to them and should be shown, versus which ones are less important and can be hidden.

You can also control stretching and shrinking at runtime via and .