Quote Originally Posted by ChrisW67 View Post
It is not clear exactly which thing "that concept" is referring to. You can build a QWizard two ways in Designer.
Referring to the method of sub-classing widgets. That's the 'concept'. This is the essence of what I am trying to do. The way I approached it seems to be the one by default project creation. That is, a wizard object that contains wizard pages all contained in a ui file. Am I wrong to assume that this is the default approach? What I think you are suggesting is an app that contains the underlying class structure that includes multiple ui files each having only one wizard page. If that is what your code sample suggested, it was jumping from what was posted.

Is it possible to extend the default approach by having classes defined for each of the wizard pages defined in the main header file created by the app wizard? If so, I was having more than my share of challenges making that work.

Thanks for the feedback. If you can post a sample of how such an approach you described is structured, I would greatly appreciate it.