> I'm tring to use a form inheriting from mmWizardForm and am having some problems. Are there any examples of using this form?

You'll notice mmWizardForm is not mentioned in the guide except in the automatically-generated class documentation. That might hint a bit. The BLG is built on it, and it really only has the code required to support writing the BLG.

Oakleaf do know this and I believe there are some improvements to come.

> Adding/removing pages. Using the events for page change?

Two areas in which the current code has some severe problems! The wizard works ok if the wizard has at least 3 pages in a strict sequence. It doesn't cope very well with dynamically adding pages. It assumes the Finish button is always enabled on the last page - and uses the page count to determine this.

Thread #1217569 may have some enlightenment.

I've subclassed mmWizardForm and also patched MM.NET core code in order to make it work. I'm not particularly keen on sharing these patches for a couple of reasons. One, I'd prefer they came via Oakleaf; and Two, I'd like it if someone would write a new set of wizard classes that are actually designed to handle more situations. The mm 2.4 classes are fundamentally simplistic, and my changes were only just enough to get my particular application operational.

If you're really keen on my patches, I supposed I could email them (you'd need to know how to patch and build your own MM.NET assemblies of course). Basically it boiled down to these

* mmWizardForm needs to derive from mmBusinessForm instead of just Form so it can hold bizobjs

* Rewrite all the next/previous button ShowCurrentPage() so it copes with fewer than 3 pages


- Walter