Advanced QTableView

[wysota]

PIMPLs ?? What do you mean.

Private implementations. All the Q***Private classes.

I've looked inside and it's difficult, so it's my last option... ( but you can never say is impossible... )

I can say it's impossible, PIMPLs are not part of the public API, so you'd have to embed half of Qt code into your widget and I don't think you want a widget with 3MB legacy in it

I disagree. I don't need ALL the interface. I f you do something like this, you have all the interface, but are allways maintaining it as a single Widget :

Well said - a widget, but not as a view. The view API is not part of the public API of the widget, so you can't make simple signal-slot connections or use the widget as a custom widget in Designer without messing around with its internals.

I only need that the improved table acts as a single widget, allowing the final developer to easily create layouts with the designer & then having a richer table in his project.

As written above, the widget will not have the API of a view, so the final developer will only have access to its QWidget API from the Designer (unless you forward all the view functionality to the widget's public API practically reimplementing the view architecture, as I mentioned in the previous post).

Why I must hide a compoenent I'm fighting to show ?

I understood you want to replace the original header view with your own header and footer. Hiding the original header would be a simple way to get rid of it. Maybe I misunderstood you.

OK, I agree too, but I must receive some signals when column header change thier size, and I don't receive nothing.

OK, but which signals ?? I've tried some combinations and I'm receiving no one...

QHeaderView::sectionResized() is an obvious candidate...