#Talent connect application wizard series

#Talent connect application wizard series

For example, what happens if Panel 3 tries to connect to a remote server and cannot make the connection? In that case, the wizard may need to branch off to another series of panels which takes the user through a setup without connecting to the server. In other words, if a wizard dialog has Panels 1 through 5, pressing the Next button four times may take you from Panel 1 to Panel 5, traversing across Panels 2, 3, and 4. First, note that wizard dialogs do not necessarily traverse across their panels in a linear fashion.Here are a few design considerations that must be kept in mind.

Seems like a simple design, right? Well, not necessarily. At any time, the user can also press the Cancel button to quit the dialog and discard any data that has been entered so far. The instantiating class should then be able to retrieve all of the data that was entered. At this point, the Next button often changes to a Finish button, and when pressed, the dialog will close. The idea here is that the application user, by pressing either the Next or Back buttons, can 'flip' across these panels, entering information on each one until he or she completes the path. In this article, I will create a framework for a simple wizard dialog that you can extend as necessary.Ī wizard dialog is constructed with a number of panels, and each panel contains user-configurable components such as radio buttons, sliders, or text fields. What exactly is a wizard dialog? Well, you've likely run across several wizard dialogs already, either when you're installing a pre-packaged application, or you're configuring a series of program options. Wizard dialogs are ubiquitous in today's desktop applications.