Changing text of button in no relation to button

[tbscope]

Always try to use the lowest common denominator.
All objects of the main window are accessible via the main window, thus change the text of a component of the main window inside a function or slot of the main window.

Example

void MainWindow::slotButtonClicked()
{
    int result = doSomething();
 
    if (result == 1) 
        button->setText("New text");
}
 
int MainWindow::doSomething()
{
    return something;
}

void MainWindow::slotButtonClicked()
{
    int result = doSomething();

    if (result == 1) 
        button->setText("New text");
}

int MainWindow::doSomething()
{
    return something;
}

To copy to clipboard, switch view to plain text mode 

[Sabre Runner]

But what if I need the ability to change the text of the button in a function that is triggered from a different button?

[Zlatomir]

You connect the second button's clicked() signal, with the slot that update the text of your first button.
Read about signals and slots

[Sabre Runner]

I'm in a hurry to get some things done, stress from the bosses and everything, I can't delve too deeply into the mechanism right now.
Why can't button.setText(text) just work as it is?

[tbscope]

It can.

Against the rules, but here's an easy answer to your homework.

class MainWindow : public something
{
    Q_OBJECT
 
public slots:
    void button1Clicked();
    void button2Clicked();
 
private
    QPushButton *button1;
    QPushButton *button2;
};
 
MainWindow::MainWindow(...) : ...
{
    button1 = new ...;
    ...
 
    connect(button1, SIGNAL(clicked()), this, slot(button1Clicked()));
    ...
}
 
void MainWindow::button1Clicked()
{
    button2->setText("Hello!");
}
...

class MainWindow : public something
{
    Q_OBJECT

public slots:
    void button1Clicked();
    void button2Clicked();

private
    QPushButton *button1;
    QPushButton *button2;
};

MainWindow::MainWindow(...) : ...
{
    button1 = new ...;
    ...

    connect(button1, SIGNAL(clicked()), this, slot(button1Clicked()));
    ...
}

void MainWindow::button1Clicked()
{
    button2->setText("Hello!");
}
...

To copy to clipboard, switch view to plain text mode 

The real question, for me, is: what are you doing coding programs at a company if you don't know basic object oriented programming?

[Lykurg]

Why can't button.setText(text) just work as it is?

Please, show the code, which isn't working for you.

[Sabre Runner]

I'm a CS student and this is my first real job programming. Thanks for the vote of confidence.

I need the ability to click a tool button, save the path taken so that other routines can use it.

void SubNyquist::on_pushFindIC_clicked()
{
    QString path = QDir::currentPath() += tr("/ic1.rbf");
    ICpath = QFileDialog::getOpenFileName(this,tr("Open IC File..."), 
         path,tr("IC Files (*.rbf)"));
    ICpath.replace(tr("/"),tr("\\"));
}

void SubNyquist::on_pushFindIC_clicked()
{
    QString path = QDir::currentPath() += tr("/ic1.rbf");
    ICpath = QFileDialog::getOpenFileName(this,tr("Open IC File..."), 
         path,tr("IC Files (*.rbf)"));
    ICpath.replace(tr("/"),tr("\\"));
}

To copy to clipboard, switch view to plain text mode 

And when a certain function, triggered by a different button, finishes correctly, they want the path displayed on the button itself.

void SubNyquist::on_pushLoadIC_clicked()
{
    ...
    doSomething(Regarding the file given)
    ...
    // And if it doesn't break in the middle...
    pushFindIC.setText(ICpath);
    ...
}

void SubNyquist::on_pushLoadIC_clicked()
{
    ...
    doSomething(Regarding the file given)
    ...
    // And if it doesn't break in the middle...
    pushFindIC.setText(ICpath);
    ...
}

To copy to clipboard, switch view to plain text mode 

[Lykurg]

ICpath.replace(tr("/"),tr("\\"));

ICpath.replace(tr("/"),tr("\\"));

To copy to clipboard, switch view to plain text mode 

If you are a CS student, then here is the first lesson: Read the documentation! (QDir::toNativeSeparators)

And are you sure pushFindIC is the right object? Because of your pices of code, I am not sure...

[Sabre Runner]

I do read the documentation but only the parts I think I need. I don't have the time to read the manual start to finish. Not right now.
And how will that work as the path given to the file dialog?

I have pushFindIC which is the Open dialog for the file to load. pushLoadIC is the button to actually load the file and do all the other things which it requires. If that doesn't break, for any reason, that is when I need to open button to change.

[Lykurg]

And how will that work as the path given to the file dialog?

It is static and takes a QString as argument?

I have pushFindIC which is the Open dialog for the file to load. pushLoadIC is the button to actually load the file and do all the other things which it requires.

Isn't pushFindIC your button? So where is the button where you want to change the text? And how do you call it? Are you using an ui file? (Seems so)

[wysota]

I don't have the time to read the manual start to finish. Not right now.

Saying such things will not get you going on this forum. Unless of course you want to hear that someone has no time to help you right now...

You should really read about signals and slots. Learning some encapsulation and building object oriented modules would be very helpful too.

[Sabre Runner]

I'll do that. I will get that first on my list. I would still appreciate any help, if and when you have time.

I am using a ui file. pushFindIC is the button for the open file dialog and the one I want to display the path in the text. pushLoadIC is the one which handles the processing of the file selected and if that process works, the path text should change.

[wysota]

What exactly do you have problems with? Which part of your task you don't know how to do? You set button labels with manipulating the QAbstractButton::text property.

[Sabre Runner]

Yes. I did that. As far as I can tell, the text is there, saved in the button's property, it just won't display in the GUI on the button itself.

My process, and I probably have no say in how this works, is that button 1 is pressed which opens the dialog to find the file. With file selected, button 2 is ready to go. Button 2 does some other things then executes a function. If that function returns correctly, then button 1's text should update to display the text it has.

Everything seems to work up to that last part of updating or notifying button 1 that it needs to update.

I'm reading the Signals and Slots tutorial now and trying to implement what I learn but so far no dice.