best practices for large forms?

[Lykurg]

I would go that way if the pages becomes complex. One main ui with the tab widget and then multiple "QWidgtes" with the content of each tab. For them also use the single inheritence. Then you have two options:
You can put the pages by hand in the tab widget (in the cpp file of your main ui) or
add empty QWidgets in the designer to your tab widget and promote them to your own created page-classes.

You always can decide if you want a tab contend to be "outsourced" or not. So it is not necessarily a definite decision. (I normaly outsource all tabs if the dialog is otherwise too complicated.)

[bajarangi]

Thanks Lykurg - this is a topic that is not covered by any of the basic tutorials and examples.

[marcvanriet]

Hi,

Someone asked a similar question some time ago. You may check out this thread : QStackedWidget-and-QTabWidget-Structure-Advice

Regards,
Marc

[bajarangi]

Very good reference. Promotion seems very useful - I have not checked it out yet.