preferences: use std::string in struct preferences

This is a messy commit, because the "qPref" system relies
heavily on QString, which means lots of conversions between
the two worlds. Ultimately, I plan to base the preferences
system on std::string and only convert to QString when
pushing through Qt's property system or when writing into
Qt's settings.

Signed-off-by: Berthold Stoeger <bstoeger@mail.tuwien.ac.at>
This commit is contained in:
Berthold Stoeger 2024-06-13 22:59:32 +02:00 committed by bstoeger
parent 82fc9de40b
commit ccdd92aeb7
78 changed files with 645 additions and 694 deletions

View file

@ -6,11 +6,11 @@
#include <QObject>
#define IMPLEMENT5GETTERS(name) \
static QString name() { return prefs.dive_computer.name; } \
static QString name##1() { return prefs.dive_computer##1 .name; } \
static QString name##2() { return prefs.dive_computer##2 .name; } \
static QString name##3() { return prefs.dive_computer##3 .name; } \
static QString name##4() { return prefs.dive_computer##4 .name; }
static QString name() { return QString::fromStdString(prefs.dive_computer.name); } \
static QString name##1() { return QString::fromStdString(prefs.dive_computer##1 .name); } \
static QString name##2() { return QString::fromStdString(prefs.dive_computer##2 .name); } \
static QString name##3() { return QString::fromStdString(prefs.dive_computer##3 .name); } \
static QString name##4() { return QString::fromStdString(prefs.dive_computer##4 .name); }
class qPrefDiveComputer : public QObject {
Q_OBJECT