QFileDialog::setDirectory does not appear to work properly in OpenSuSE 11.3 QT 4.6.3

[crubel]

Just a quick note to add to this thread..

This morning I installed the latest SDK 4.7, rebuilt the app I have attached
to my previous post. Verified that it was using the newly installed QT libraries
and not the version installed via openSuSE.

Same result, the file dialog still insists on opening in the same dir you start
the app from instead of where it was set to go to...

[ChrisW67]

You are trying to mix the static getOpenFileName() convenience function, which expects to get the working directory in its calling parameters, and using the dialog exec() or show() methods.

Try either the static approach:

void MainWindow::on_pushButton_clicked()
{
    QString fileName = QFileDialog::getOpenFileName(this,
        tr("Open File"), 
        "/tmp", 
        tr("All Files (*.*)")
    );
 
    if ( filename.isEmpty() )
        return;
}

void MainWindow::on_pushButton_clicked()
{
    QString fileName = QFileDialog::getOpenFileName(this,
        tr("Open File"), 
        "/tmp", 
        tr("All Files (*.*)")
    );

    if ( filename.isEmpty() )
        return;
}

To copy to clipboard, switch view to plain text mode 

or the conventional dialog approach

void MainWindow::on_pushButton_clicked()
{
    QFileDialog dialog;
    QString filename;
 
    dialog.setDirectory( "/tmp" );
    dialog.setFileMode(QFileDialog::ExistingFile);
    if (dialog.exec()) {
        QStringList filenames = dialog.selectedFiles();
        filename = filenames.at(0);
    }
    else
        // dialog rejected
}

void MainWindow::on_pushButton_clicked()
{
    QFileDialog dialog;
    QString filename;

    dialog.setDirectory( "/tmp" );
    dialog.setFileMode(QFileDialog::ExistingFile);
    if (dialog.exec()) {
        QStringList filenames = dialog.selectedFiles();
        filename = filenames.at(0);
    }
    else
        // dialog rejected
}

To copy to clipboard, switch view to plain text mode 

The behaviour is inconsistent if you mix the two it would seem.

[crubel]

SOLVED -- Thank you very much -- ChrisW67

Making the changes as you suggested has solved this issue for us.

Again thanks for the help and the explanation to the cause of the
problem. Seems no one here caught that mix of the two separate
approaches, not to mention throwing us off because it had worked
in the older versions of QT and KDE.

Curtis