QSettings rewriting the .ini file, so not able to restore the values

[DURGAPRASAD NEELAM]

When I am using below code on Linux SLES 11 machine the .ini file is recreating for some reason so that I am not able to restore my settings.
Same code working fine on Windows machine.

Prb: I want to have recently opened file list on start up window, so that user can select quickly.

Window::Window()
{
     restoreRecentFileList();
}
 
Window::~Window()
{
      saveRecentFileList();
}
 
void Window::saveRecentFileList()
{
    QSettings settings(m_settingsPath, QSettings::NativeFormat);
    settings.setValue("recentFiles/list", QVariant(m_recentFilesList));
}
 
void Window::restoreRecentFileList()
{
    QSettings settings(m_settingsPath, QSettings::NativeFormat);
    m_recentFilesList = settings.value("recentFiles/list").toStringList();
}
 
void Window::openFile(QString l_file)
{
 
    if(isValidFile(l_file))
    {
        m_recentFilesList << l_file;
 
        done(QDialog::Accepted);
        qDebug() << "connected to : " << l_file;
    }
    else
    {
       QMessageBox::information(this, "Information", "Please choose valid file", QMessageBox::Ok);
    }
}

Window::Window()
{
     restoreRecentFileList();
}

Window::~Window()
{
      saveRecentFileList();
}

void Window::saveRecentFileList()
{
    QSettings settings(m_settingsPath, QSettings::NativeFormat);
    settings.setValue("recentFiles/list", QVariant(m_recentFilesList));
}

void Window::restoreRecentFileList()
{
    QSettings settings(m_settingsPath, QSettings::NativeFormat);
    m_recentFilesList = settings.value("recentFiles/list").toStringList();
}

void Window::openFile(QString l_file)
{

    if(isValidFile(l_file))
    {
        m_recentFilesList << l_file;

        done(QDialog::Accepted);
        qDebug() << "connected to : " << l_file;
    }
    else
    {
       QMessageBox::information(this, "Information", "Please choose valid file", QMessageBox::Ok);
    }
}

To copy to clipboard, switch view to plain text mode 

//when i print m_recentFilesList , i am able to see expected values

on 1st run of Application:     no .ini file                                 ,  after closing App : .ini file have 1 file name stored in it
on 2st run of Application:    .ini file have 1 file  name stored in it        ,  after closing App : .ini file have 1 file name stored in it
on 1st run of Application:    .ini file is empty                                    ,  ini file is empty

on 1st run of Application:     no .ini file                                 ,  after closing App : .ini file have 1 file name stored in it
on 2st run of Application:    .ini file have 1 file  name stored in it        ,  after closing App : .ini file have 1 file name stored in it
on 1st run of Application:    .ini file is empty                                    ,  ini file is empty

To copy to clipboard, switch view to plain text mode 

[ChrisW67]

Based on the code you posted m_settingsPath, which we have to assume is a member variable of the class, has not been initialised at the time restoreRecentFileList() is called.

[DURGAPRASAD NEELAM]

Sorry, I forgot to update that, here is the constructor actually

Window::Window(QWidget *parent) : QDialog(parent),
m_settingsPath(QDir::homePath() + QString::fromUtf8("/.cfg/recentFiles.ini"))
{
//m_settingsPath is a member variable of the class
}

[ChrisW67]

What actually gets into the ini file?

BTW: QDir::homePath() may not be where you think it is if there is no HOME environment in the running program's environment.

[anda_skoa]

BTW: QDir::homePath() may not be where you think it is if there is no HOME environment in the running program's environment.

While I don't think it is likely that QDir::homePath() does not return something usable, the proper location for config files is of course the writable location of QStandardPaths::ConfigLocation.

Cheers,
_

[DURGAPRASAD NEELAM]

There is something wrong with my Environment I think, It's working as expected on another SLES machine, sorry for that and thanks for the effort.

[ChrisW67]

Another possibility is that your code constructs two Window objects (deliberately or not), one is actively used, the other is dormant so keeps the originally loaded list, and the last one to be destroyed wins. Stick a breakpoint/qDebug() in the destructor to see how many objects of this class are destroyed as you leave the program.