The obvious use for data binding: A table.
The database table has 11 columns/fields.
I want to show 3 of these only in an initial view (the idea being that double-clicking on a row of the table control navigates to a ‘detail’ page showing all fields).
Attempt 1: I created the 3 fields in the table control from within the property inspector. I set the sizes appropriately (field 1 needs about 70% of the width). On setting the databinding, the table loses its mind and shows all fieds in now small columns that can’t be resized.
Attempt 2: I added all fields and hide the ones I don’t want to show. Same again.
Editing the column list makes the table regain its senses temporarily (ie showing the 3 column as desired) but after a few seconds it reverts to showing all 11 columns with small fixed widths.
As an aside: Is it possible to express the width of a column as a percentage of the width of the table automatically? (ie instead of saying 600 px, it could be 70%?)
As it stands I’m either dong something terribly wrong, or this is a major bug…
Any suggestions?
The column visibility and widths can’t be edited within the PI.
If I add these columns manually, the settings are ignored with databinding (ie visibility and column width is not respected and labels are ignored).
I tried to be clever and added a dataView with on the 3 columns, and I got this instead:
Again: the settings are ignored with databinding (ie visibility and column width is not respected and labels are ignored). Also, the order of the columns is fixed alphabetical. Not great…
And to re-iterate a feature request: Would be great if column widths could be set as a percentage of the control width (obviously taking into account borders etc).
There are quite a few issues with the table widget at the moment which we are aware of but hoping to have fixes soon. I will file a suggestion for the percentage based column widths. Thank you for the feedback!
