Changing text of button in no relation to button

[ChrisW67]

It appears you want the user to push button 1 to select a file. You then change the label on button 1 to the path the user selected. You then expect the user to push button 2 to process the file selected when they pushed button 1.

Quoting out of order:

What I'd like to do is to change the text of button 1 if and only if button 2's operation has reached the loaded successfully part.

Then why do you set it in the handler for the pushButton1 clicked signal? Line 5 in this chunk:

void Window::on_pushButton1_clicked()
{
    path = QFileDialog::getOpenFileName(this, tr("Open File..."), path,tr("Files (*.*)"));
    path = QDir::toNativeSeparators(path);
    pushButton1.setText(path);
}

void Window::on_pushButton1_clicked()
{
    path = QFileDialog::getOpenFileName(this, tr("Open File..."), path,tr("Files (*.*)"));
    path = QDir::toNativeSeparators(path);
    pushButton1.setText(path);
}

To copy to clipboard, switch view to plain text mode 

This is the button that preps the path to be used to load the file from.

should probably be after line 16 of this chunk where the processing has been successful after the user presses button 2:

void Window::on_pushButton2_clicked()
{
    try something...
    catch one exception...
    {
        output error 1...
    }
    catch second exception...
    {
        output error 2...
    }
    catch all other exceptions...
    {
        output generic error...
    }
    QMessageBox::information(this,tr("Loaded"),tr("Loaded Successfully"));
    perform some other operations and configurations for the future...
}

void Window::on_pushButton2_clicked()
{
    try something...
    catch one exception...
    {
        output error 1...
    }
    catch second exception...
    {
        output error 2...
    }
    catch all other exceptions...
    {
        output generic error...
    }
    QMessageBox::information(this,tr("Loaded"),tr("Loaded Successfully"));
    perform some other operations and configurations for the future...
}

To copy to clipboard, switch view to plain text mode 

You also need to ensure that button 2 cannot be pressed unless button 1 has been AND the user did not cancel the file selection. Something has to reset button 1's label too I guess.

[SixDegrees]

I hate to keep suggesting "printf-style" debugging, but here's another case where it would probably shed light on what's going on. Placing output statements in your code just prior to your call to button.setText() would allow you to see if that portion of your code is getting called in the first place, and if so to dump the value of local variables that may be related to your problems.

The preferred method for determining such things, of course, is to run in a debugger, but for simple problems it's often best to use simple solutions.

Also, I should point out that trying to display paths on buttons is a remarkably poor UI decision. As soon as you hit a case where the path is too long to show on the button, and you realize that you can't scroll to see the other end of it, the design breaks and breaks badly. And that's probably going to happen within minutes of actual use.

Part of your job as a software engineer will be to bring such matters to a client's attention before they cause such problems, and to provide reasonable alternative solutions.

[Sabre Runner]

Yes. I even added that same set text command at the start of the program but it doesn't change the button.
Do I need to update or repaint? And if so, how? Because I tried those some times and they didn't work either.