[SOLVED] save and restore window / dialog positions

kalster

I am have a problem with line 24 / 25 of the code. I am getting the error mainwindow.cpp:24: error: 'saveGeometry' was not declared in this scope and mainwindow.cpp:25: error: 'saveState' was not declared in this scope.

do i have to create the saveGeometry and saveState functions? I need examples for this code please.

@#include "mainwindow.h"
#include "ui_mainwindow.h"
#include <QWidget>
#include <QSettings>

MainWindow::MainWindow(QWidget *parent) :
QMainWindow(parent),
ui(new Ui::MainWindow)
{
ui->setupUi(this);
QSettings settings;

restoreGeometry(settings.value("mainWindowGeometry").toByteArray());

// create docks, toolbars, etc...

restoreState(settings.value("mainWindowState").toByteArray());

}

void closeEvent(QCloseEvent *event) {
QSettings settings;
settings.setValue("mainWindowGeometry", saveGeometry());
settings.setValue("mainWindowState", saveState());
}

MainWindow::~MainWindow()
{
delete ui;
}@

mlong

Line 22 should be:

@
void MainWindow::closeEvent(QCloseEvent *event) {
@

kalster

thank you Mlong.

I changed line 22. run the program and i do not get any errors. Yet the code is not saving the main window position. what am i doing wrong?

kalster

i solved it. i needed the following code in the main.cpp file

@ QCoreApplication::setOrganizationDomain("OrgDomain");
QCoreApplication::setOrganizationName("OrgName");
QCoreApplication::setApplicationName("AppName");
QCoreApplication::setApplicationVersion("1.0.0");@

mlong

Glad it's working! (Be sure and use meaningful values in your Organization & App domains and names.)

kalster

ok, I will. thank you

kalster

"here":http://developer.qt.nokia.com/doc/qt-4.7/qapplication.html#id-7292984e-d337-4916-bbdf-6b5499d193c1 is the link from the save state quote below
[quote]This function deals with session management. It is invoked when the session manager wants the application to preserve its state for a future session.

For example, a text editor would create a temporary file that includes the current contents of its edit buffers, the location of the cursor and other aspects of the current editing session.

You should never exit the application within this function. Instead, the session manager may or may not do this afterwards, depending on the context. Futhermore, most session managers will very likely request a saved state immediately after the application has been started. This permits the session manager to learn about the application's restart policy.[/quote]

one last question. above is a quote about saveStates. the savestate code that I have in my program (see below code), will my program exit within this saveState function?

@settings.setValue("mainWindowState", saveState());@

mlong

I'm not sure exactly what you're asking.

The saveState() won't ever cause your program to exit.

However, when the above program exits, the closeEvent() will be called as the window is closed and, thus, saveState() will be called.

kalster

the save state quote above is saying that You should never exit the application within this save state function. is my code exiting within the save state function?

redkite

no, your code is exiting after saveState(), when closeEvent() is ended.

This warning is only for people who re-implement the saveState() fucntion, it's not your case, you are using the original one.

kalster

thank you redkite. i marked this topic as solved.