> but don't think it would have made anything simpler
well, here is a common case I think :
the number of columns and their names depends on the type of data the TableListModels point to (or contain).
when a TableListModel is given to a table through table->setModel() then you also have to set up all your header with many many table->getHeader()->…
And if you use different tables to which you want to give that model, that can be quite a lot of lines..
and if you want to change your table model in runtime, you have to do that again.
I can't have a component which inherits TableList and implements that logic, because if the table does not know what TableListModel will show, it won't be able to set up its header correctly.
If the header was set up in the model that would be done automatically, or we could just call something like updateHeader().
but again, maybe I'm not approaching that the right way?