How to hide all wizard buttons

[roseicollis]

Hi,

I have a wizard app with its wizardpages and in some of them, I want to hide ALL wizardbuttons.

My wizard is declared this way:

class BaseWizard : public QWizard

class BaseWizard : public QWizard

To copy to clipboard, switch view to plain text mode 

And I've tried this on the constructor:

BaseWizard::BaseWizard(QWidget *parent) :
    QWizard(parent),
    ui(new Ui::BaseWizard)
{
 
    this->button(QWizard::NextButton)->setVisible(false);
    this->button(QWizard::CancelButton)->setVisible(false);
    this->button(QWizard::BackButton)->setVisible(false);
    this->button(QWizard::FinishButton)->setVisible(false);
    this->button(QWizard::CustomButton1)->setVisible(false);

BaseWizard::BaseWizard(QWidget *parent) :
    QWizard(parent),
    ui(new Ui::BaseWizard)
{

    this->button(QWizard::NextButton)->setVisible(false);
    this->button(QWizard::CancelButton)->setVisible(false);
    this->button(QWizard::BackButton)->setVisible(false);
    this->button(QWizard::FinishButton)->setVisible(false);
    this->button(QWizard::CustomButton1)->setVisible(false);

To copy to clipboard, switch view to plain text mode 

And also with setEnabled(false) and with hide() and yes, Cancel, and CutomButton disappear BUT Next and Back always remain there. I tried to put it too in the initializepage() of the wizardpage but its the same.

Any idea of why do that buttons saty there? Or what am I doing wrong?

Thank you so much!

[ChrisW67]

Aside from the question of how you are supposed to navigate a wizard with no buttons... the Next button is controlled by the return value of nextId(). The Back button will likely be made visible if you navigated to this page from another.

[roseicollis]

how you are supposed to navigate a wizard with no buttons

Well in some pages I have my own buttons and as the interaction is full with keyboard that means that they user goes to the next page with Enter/Return key and back with backspace. So in that cases, wizard's buttons annoy more than anything cause they have no function and there is no reason to have something which has no use and can confuse the user.

he Next button is controlled by the return value of nextId()

Okey... so.... how can I 'not show that button' in a wizardpage?

The Back button will likely be made visible if you navigated to this page from another.

First it didn't work.. as I said I tried with all buttons and back and next always stays there -.-'' and second.... what about the first page?

Thank you!

[d_stranz]

So why don't you just live with the buttons and cause the Enter and Backspace keys to cause clicks on the Next and back buttons?

I agree with ChrisW67 - you are implementing a very weird QWizard. If you don't like the standard behaviour, then why not just emulate a QWizard with a set of pages in a custom QStackedWidget? You would have absolute control over which page is shown when without having to worry about all those pesky buttons.

[wysota]

Well in some pages I have my own buttons and as the interaction is full with keyboard that means that they user goes to the next page with Enter/Return key and back with backspace. So in that cases, wizard's buttons annoy more than anything cause they have no function and there is no reason to have something which has no use and can confuse the user.

So why are you using a wizard at all? Why not have a QStackedWidget with a bunch of pages?

[roseicollis]

So why don't you just live with the buttons and cause the Enter and Backspace keys to cause clicks on the Next and back buttons?

Well.. it would be so extrange that in some pages you have next and back button for no reason... I have already implemented the behaviour of enter but its ugly to have things on the screen for no reason and that if you focus them, they do nothing (because the focus would be on them and not in any option of the screen)

So why are you using a wizard at all? Why not have a QStackedWidget with a bunch of pages?

The reason for that is that a work mate told me to do it with wizard structure so I did it. I suppossed that it was the best option and moreover, I never saw before the class StackedWidget until u mentioned it O.o I'll try to go with the wizard 'cause I have to finish that and I have no time to try to change it into a QStackedWidget but I will consider that in the futur or later if I need it.

One question... if a QStackedWidget can have a lot of widgets and pages like the wizard... does that mean that I can use the same pages I have already on the wizardpage? I mean: Now I have a QWizard with a lot of QWizardPages... so could I have a QStackedWidget with a lot of QWizardPages? and so the change is just so little? Or would it be much more complicated?

Thank you !!

[wysota]

The wizard is implemented over QStackedWidget so basically yes, you can reuse your pages. Just remember wizard() will then return null.

[roseicollis]

Just remember wizard() will then return null.

What do you mean with that?

Another thing: On the QWizard constructor I have this:

this->button(QWizard::NextButton)->setFocusPolicy(Qt::TabFocus);

this->button(QWizard::NextButton)->setFocusPolicy(Qt::TabFocus);

To copy to clipboard, switch view to plain text mode 

I'm trying to set focus policy Qt::NoFocus on that wizardpages were I don't want to have that buttons (so at least user will see them but won't reach them with tab), on its constructors or initializePage() but the program ignores me. It always do what I put on the QWizard class constructor.

For example:

QWizard constructor: this->button(QWizard::NextButton)->setFocusPolicy(Qt::TabFocus);
QWizardPage 1 where I don't want the buttons: wizard()->button(QWizard::NextButton)->setFocusPolicy(Qt::NoFocus);
QWizardPage 2 where I want the buttons again: wizard()->button(QWizard::NextButton)->setFocusPolicy(Qt::TabFocus);

result: on wp 1 and wp 2 its like setFocusPolicy(Qt::TabFocus);

So... can't I switch between focuspolicies?

Thank you!

[wysota]

What do you mean with that?

I mean QWizardPage::wizard() is not going to return a valid wizard pointer if you are not going to have a wizard but a stacked widget instead.

[ChrisW67]

I'm trying to set focus policy Qt::NoFocus on that wizardpages were I don't want to have that buttons (so at least user will see them but won't reach them with tab), on its constructors or initializePage() but the program ignores me. It always do what I put on the QWizard class constructor.

It is evident that you do not want the features of QWizard so stop tryng to bend it to your will and simply reimplement your multi-page dialog using QStackedWidget and whatever other logic you want. Switching approach is less effort than you have put into this thread.

[d_stranz]

It's funny how some of us (and I am guilty as well) are so resistant to throwing out ineffective code that "sort of works but not really", when it is obvious (even while I am being resistant) that just biting the bullet and throwing it out would result in something that is so much cleaner and maintainable. Pack rat mentality, I suppose.

[wysota]

I never hestitate to throw away everything I've got and start from scratch. Unfortunately (at least for me) my workmates rarely share my point of view. How do you tell your boss that the thing you've been working on for the last two weeks should be trashed. And how do you explain you will just need two days to rewrite it? "So what have you been doing during those two weeks?"