feature request #7659
Implement algorithm to optimize initial column size in NAT tables
If a NAT table has multiple columns the correct initial column size becomes important to avoid too much empty space at one hand and too much manual resizing at the other side.
First of all scrolling needs to be switched on (implemented in #7518).
Many possible algorithms to set the initial column sizes can be developed.
One idea could be to compute for the first query the median of the text length of all results. Then use this median to compute the percentage of the column size.
Probably we should not resize columns after they have once manually been changed after a previous query as the sizes might be wanted as they are.