cleanup: fix initialization order in QMLProfile constructor

The compiler complains that members were initialized out-of-order.
Even though this is not an issue here it is correct to emit a
warning, since only then it is guaranteed that the objects are
destructed in reverse-order with respect to construction.

Signed-off-by: Berthold Stoeger <bstoeger@mail.tuwien.ac.at>
This commit is contained in:
Berthold Stoeger 2020-03-30 20:38:27 +02:00 committed by Dirk Hohndel
parent 38d70ba854
commit 45a3fff62c
2 changed files with 2 additions and 3 deletions

View file

@ -264,7 +264,6 @@ private:
bool checkDepth(const DiveObjectHelper &myDive, struct dive *d, QString depth);
int openAndMaybeSync(const char *filename);
bool currentGitLocalOnly;
Q_INVOKABLE DCDeviceData *m_device_data;
QString m_progressMessage;
bool m_btEnabled;
void updateAllGlobalLists();

View file

@ -14,9 +14,9 @@ QMLProfile::QMLProfile(QQuickItem *parent) :
QQuickPaintedItem(parent),
m_devicePixelRatio(1.0),
m_margin(0),
m_profileWidget(new ProfileWidget2),
m_xOffset(0.0),
m_yOffset(0.0)
m_yOffset(0.0),
m_profileWidget(new ProfileWidget2)
{
setAntialiasing(true);
setFlags(QQuickItem::ItemClipsChildrenToShape | QQuickItem::ItemHasContents );