You could try the CardLayout manager, which is modeled after java's CardLayout
manager. I think it comes with the Win32::GUI distribution now a days. It works
by giving all of the widgets that are located on the same screen the same
identifier. Since they all have the same page identifier you can "flip" between
screens. I don't know any of the performance issues of creating and destroying
windows vs. the CardLayout. But either way you could look in that direction as a
solution to your first idea instead of destroying controls.
there is a small example in cardlayout.pm of the distribution.
Hope this helps
Mike Kangas
[EMAIL PROTECTED]
Ian Taite wrote:
> I want to design a GUI for walking through creating an NT account according
> to local standards/requirements. Replacing our command line version with a
> GUI version presents some general programming problems which I must solve if
> I am to write this and other GUI wizard-based apps.
>
> I am new to Win32-GUI however, I have gone through some of the gui-tut pages
> and I am capable of getting a dialogue window on screen with some carefully
> positioned labels and buttons, along with processing user actions.
>
> Which approach should be taken for designing wizards? Two approaches spring
> to mind.
>
> I could have a single window on which I create and destroy controls to give
> the illusion of different steps or pages the user must go through. This
> might use minimum resources but would be hard to code, test and debug as
> well as probably being slow.
>
> I could have one window per step in the wizard.
>
> There are pros and cons to both methods.
>
> Can anyone recommend how I might design this solution?
>
> Regards,
> Ian.
