Qt-solutions Archive, July 2006
Pretty slimy QT Solution
Message 1 in thread
Im sorry, but in QT 3, QT had a QWizard class. In QT 4, it got pulled.
With the following comment in the migration from 3-4 documentation:
"In Qt 4 applications, you can easily obtain the same result by
combining a QStackedWidget
<file:///C:\Documents%20and%20Settings\scott\My%20Documents\Visual%20Stu
dio%20Projects\tot\win32\ThirdParty\Qt\4.1.2\doc\html\qstackedwidget.htm
l> with a QDialog
<file:///C:\Documents%20and%20Settings\scott\My%20Documents\Visual%20Stu
dio%20Projects\tot\win32\ThirdParty\Qt\4.1.2\doc\html\qdialog.html> and
provide QPushButton
<file:///C:\Documents%20and%20Settings\scott\My%20Documents\Visual%20Stu
dio%20Projects\tot\win32\ThirdParty\Qt\4.1.2\doc\html\qpushbutton.html>
s yourself.":
Which is not really the case, its quite often a pain in the butt to get
all the logic correct for a wizard. But they did ship 2 examples a
Simple and Complex Wizard...
Now they moved the Wizard into the QT4 solutions set...
It just seems a bit slimy... I should be placed in the normal QT 4.2
code base. It certainly is not a solution, is base functionality. It
seems the TT is trying to nickel and dime people.
It certainly is not "code less create more"
Scott
Message 2 in thread
Dear Scott Aron,
> Which is not really the case, its quite often a pain in the butt to get
> all the logic correct for a wizard. But they did ship 2 examples a
> Simple and Complex Wizard…
>
> Now they moved the Wizard into the QT4 solutions set…
>
> It just seems a bit slimy… I should be placed in the normal QT 4.2 code
> base. It certainly is not a solution, is base functionality. It seems
> the TT is trying to nickel and dime people.
We basically agree with you. The reason we released QtWizard as a
solution and not as a Qt 4.2 class is that we wanted to get some
feedback about its design (especially the "mandatory fields" mechanism).
It is likely that QtWizard will be moved into Qt in a later version
(e.g. 4.3).
Regards,
Girish
--
[ signature omitted ]
