qtcore

I'm trying to learn how to serialize QMap objects in windowed applications, using this code: #include "mainwindow.h" #include "ui_mainwindow.h" #include <QFile> #include <QString> #include <QDataStream> #include <QMap> #include <QDebug> void write () { QString filename = "Z:/snippets.txt"; QFile myFile (filename); if (!myFile.open(QIODevice::WriteOnly)) { qDebug() << "Could not write " << filename; return; } QMap<QString,QString> map; map.insert("one","this is 1"); map.insert("two","this is 2"); map.insert("three","this is 3"); QDataStream out (&myFile); out.setVersion(QDataStream::Qt_5_3);

#include "mainwindow.h" #include "ui_mainwindow.h" #include <QSettings> #include <QDebug> MainWindow::MainWindow(QWidget *parent) : QMainWindow(parent), ui(new Ui::MainWindow) { ui->setupUi(this); QSettings * qsettings = new QSettings(":/config.ini",QSettings::IniFormat); bool status = qsettings->value("preview","").toBool(); qDebug() << status; } MainWindow::~MainWindow() { delete ui; } Once i could do it but now i don't know whats wrong. When i googled this problem i just saw that this impossible but i enshure that i did it before. This works like a charm for me: main.qrc <!DOCTYPE RCC><RCC

I wonder, how can I use multiple- or sub-arguments with QCommandLineParser ? For example: /home/my_app --my_option_with_two_params first_param second_param --my-option-with-one-param param? Try this which has the analogy of -I /my/include/path1 -I /my/include/path2 : --my_option_with_two_params first_param --my_option_with_two_params second_param ... and then you can use this method to have access to the values: QStringList QCommandLineParser::values(const QString & optionName) const Returns a list of option values found for the given option name optionName, or an empty list if not found. The

I am porting a Linux app to Windows written in Qt. The application needs to save some settings before closing. On Linux, we can do that by signal handlers for SIGTERM etc. How can I implement the same on Windows. If you are using the Qt event loop, you can catch the following signal: void QCoreApplication::aboutToQuit() [signal] This signal is emitted when the application is about to quit the main event loop, e.g. when the event loop level drops to zero. This may happen either after a call to quit() from inside the application or when the users shuts down the entire desktop session. The signal