![]() |
Wizard dialog class? |
Post Reply ![]() |
Author | |
ibmldev ![]() Groupie ![]() Joined: 17 October 2006 Status: Offline Points: 19 |
![]() ![]() ![]() ![]() ![]() Posted: 21 July 2008 at 11:18am |
Is there any sort of wizard dialog class in ToolkitPro? I am making a wizard application that will guide the user through various steps, with "Next" and "Back" buttons, etc. Has Codejock made such a class already?
I have written wizards by hand before, but it would be nice to have a neat class to base this on. I saw a post in this forum about making the tab control "hideable", so you could effectively tab between pages but hide the actual tabs, so the effect is much like a wizard. Was that implemented (I have 12.0.0) already? If so, can you furnish a small example on adding tabs and hiding the control? |
|
![]() |
|
Oleg ![]() Admin Group ![]() Joined: 21 May 2003 Location: United States Status: Offline Points: 11234 |
![]() ![]() ![]() ![]() ![]() |
Hello,
We don't have wizard class. think standard CPropertySheet + Wizard mode can do most of work.
|
|
Oleg, Support Team
CODEJOCK SOFTWARE SOLUTIONS |
|
![]() |
|
DLewanda ![]() Newbie ![]() Joined: 10 September 2008 Status: Offline Points: 7 |
![]() ![]() ![]() ![]() ![]() |
I was looking to convert a class derived from CPropertySheet that is used in a wizard to instead be derived from CXTPPropertySheet. Upon doing so, however, I noticed that CXTPPropetySheet derives from CDialog, not CPropertySheet as I expected. This would be okay except that CPropertySheet provides a function SetWizardButtons for enabling and disabling the BACK and NEXT buttons. How would I do this if I derive from CXTPPropertySheet?
|
|
![]() |
|
Oleg ![]() Admin Group ![]() Joined: 21 May 2003 Location: United States Status: Offline Points: 11234 |
![]() ![]() ![]() ![]() ![]() |
CXTPPropertySheet can't work with Wizard Mode. Use standard CPropertySheet.
|
|
Oleg, Support Team
CODEJOCK SOFTWARE SOLUTIONS |
|
![]() |
|
DLewanda ![]() Newbie ![]() Joined: 10 September 2008 Status: Offline Points: 7 |
![]() ![]() ![]() ![]() ![]() |
Okay, fair enough. The reason I was pursuing this was to be able to leverage the resizability of the CXTPPropertyPage to avoid having to maintain that all the pages are fixed to the same size. I don't believe I can use the CXTPPropertyPage without putting it in a CXTPPropertySheet. Is this correct? Is the easiest solution to accomplish the resizing question just to have my CPropertyPage derivative inherit from XTResize directly? If so, does my CPropertySheet derivative need to do the same? Or is there another way to leverage the resize feature?
|
|
![]() |
|
snidelys4 ![]() Newbie ![]() ![]() Joined: 16 June 2011 Status: Offline Points: 1 |
![]() ![]() ![]() ![]() ![]() |
Is there any better way of doing this now? Any sample? |
|
Product: SkinFrameworkBundle 18.2.0
Platform: Windows XP SP3 Language: C++ in VS2010 |
|
![]() |
|
link ![]() Groupie ![]() Joined: 02 July 2009 Status: Offline Points: 20 |
![]() ![]() ![]() ![]() ![]() |
Is there support for this now?
Toolkit Pro 15.2.1
XP
C++ in VS2008
|
|
![]() |
Post Reply ![]() |
|
Tweet
|
Forum Jump | Forum Permissions ![]() You cannot post new topics in this forum You cannot reply to topics in this forum You cannot delete your posts in this forum You cannot edit your posts in this forum You cannot create polls in this forum You cannot vote in polls in this forum |