Wizard bug fixes

Fixes #1332
Fixes #1333 
I don't think that ( qt-project.org/doc/qt-4.8/objecttrees.html  ) applies for what I am talking about. In the examples below they are variables declared on the stack so their memory is freed by simply going out of the function scope. At the beginning of the article they use the word destroy but I think they are referring to removing it from the visual hierarchy.

When you allocate an object with ```new``` then something has to call ```delete``` on it. There are some frameworks that have built in object tracking and garbage collection (e.g. openscenegraph has this), but the link you supplied doesn't say Qt does. Searching for Qt and garbage collection doesn't find anything either.

Just making this a class variable (not pointer) would be an easy solution, since multiple instances aren't used.