One potential enhancement is simply to have the navigation stored on a stack. The Back button would then simply pop pages off the stack. This would make the later pages much simpler, because they wouldn't need to know where to return to.
To simplify it further than that, one might decide to discard the simple list of pages, and to replace it with a collection of lists. That is: if the user chooses option B on the first page, then all of the next pages come from this other list. I'm not sure how well that'll scale.
To be honest, if I ever get time, I'll be revisiting this project to update the styling to the one that MS are using these days, rather than the (dated-looking, but still cool) Wizard97 style. At the same time, I might see if I can do some separation-of-concerns stuff -- i.e. look at an MVC or MVP or MV-VM pattern for this stuff.
Re: Flow Style
One potential enhancement is simply to have the navigation stored on a stack. The Back button would then simply pop pages off the stack. This would make the later pages much simpler, because they wouldn't need to know where to return to.
To simplify it further than that, one might decide to discard the simple list of pages, and to replace it with a collection of lists. That is: if the user chooses option B on the first page, then all of the next pages come from this other list. I'm not sure how well that'll scale.
To be honest, if I ever get time, I'll be revisiting this project to update the styling to the one that MS are using these days, rather than the (dated-looking, but still cool) Wizard97 style. At the same time, I might see if I can do some separation-of-concerns stuff -- i.e. look at an MVC or MVP or MV-VM pattern for this stuff.
Or I could just redo the lot in WPF...