is the title part(the top) part of the wizard?

Yes it is.

I will make it optional.

other question if you have for example 5 steps can you jump from step 1 to say step 4?

I like the title looks very professional

I ask this because of the Entry in keepass that I was talking about yesterday

Committed.

@ron Yes, you can jump between steps as well. For example, you can inject the Wizard and set

currentPage

to whatever you want.

yes but looking at that nice left panel, can those steps be like links?

@ron Yes, I will add the option to make them links 🙂

nice I see potential for my UI

Great! Adding some features, back soon.

@edvin The wizards look really nice... I am gone try them out tonight.. regarding the resizing, would it possible to find out the maxsize for all the steps, before make them visible are loading them to determine the preSize for all the steps, then the size would not jump between steps?

@nimakro Great! And perfect idea! I will do just that!

I also have a small issue with the

InstanceScope

. Looking up the wizard from pages will now yield yet another Wizard.. hehe 🙂 Need to circumvent that.

Probably by checking if there is a Wizard in the current scope, then return that.

Lunch first!

@User uploaded a file:

Still working on the resizing feature, will continue later today.

Just committed:

Wizard content respects size of largest page

I found this to be the easiest solution:

@User uploaded a file: Add all children to center stackpane, show only currentPage

Since all the children are managed, the stack pane correctly calculates the required size. I tried several much more elaborate schemes before I ended on this pretty simplistic solution 🙂

Some times I forget all the nice shortcuts we have added to the framework, or over complicate things.

Trying to come up with a nice use case to demonstrate the Wizard. Any suggestions?

I could just go with the customer/contact thing from above of course, but I always to that.

customer/contact gets the point across I think...

I will try Customer Basic Data on page one and Address data on page two to keep it light. That also brings me to another issue that needs to be addressed. If you share a CustomerModel between those two pages, you might not be able to commit page one, because page two uses the same customer model and hence the same validation context. One solution is to not share a model between the wizard pages, another is to support partial commit, so you choose what fields you want to commit. I kind of like that idea.

There seem to be a bug in the Steps legend. It doesn't always update to show the new current page in bold.

@edvin - my first reaction is that a shared model is easier to understand - I guess you would only validate what your are going to commit (or partially commit)?