How to hide all wizard buttons

[roseicollis]

Ohhhhhhhhhh shit... forgot to comment that line... -.-''

The line its created by Qt when I create the class and I always comment it, but this time I didn't see it... my fault... I was blind thinking about the layouts and didn't see that.

Thank you!

Edit: One more thing: In wp1 I have 2 buttons, do you know why do they appear at the bottom of the page and not at the top? I mean.. now is like if there were gravity and buttons go as down as they can while before, with QWizard they were as 'up' as they can.

[d_stranz]

The code you have written for your StackedWidget class makes no sense at all.

A stacked widget is just an empty container for holding a collection of other widgets. The collection is like deck of cards, and only one card can be visible at a time. The code you wrote adds three cards to the deck: the first one of type WP1, the next two of type QPushButton.

Then you do something weird with a combo box in a layout and you set that as a "central widget", whatever that is. Is it a new widget in the stack?

If I can try to look inside your mind, it appears that what you might want to do is to have a combo box that lets you choose which widget in the stack you want to be visible. In that case, you don't want that combo box to be in the stack of widgets at all, you want it to be external to it.

So if that's what you want, then create a new class, derived from plain old vanilla QWidget, add a QVBoxLayout to it, put the combobox on top and a plain old vanilla QStackedWidget in the bottom. In the constructor for this widget, fill in your combo box, create the widgets that will serve as the cards in your stack, and choose which one appears first.

If you want to keep the design flexible, if you have widgets in the stack that need to control which page is shown next (click a button on page 1 that causes page 3 to be shown), then expose that click to the top level widget using a custom signal, and let the top level widget tell the stack which page to show next. If you push this logic down into the individual pages (as you appeared to have been doing), then you end up with a rat's nest of interdependent code.

Signals and slots help you modularize things and make it so that the only widgets that need to know the details of what's going on are the ones in charge. All the little low-level widgets just do their thing and tell the guys in charge (via signals) that something has happened that they might want to pay attention to.

Look a QPushButton - does it care what widget it is inside of? No. It's whole job is to display its label and icon and to let whoever cares know when someone has clicked it. Your page widgets should act the same way.

[roseicollis]

Thanks d_stranz,

That example was so clear