core: fix connect call

Fix multiple run-time errors in connect call introduced in 504e912512.
1) Set the proper signature of the signal. 2) make the used slot
a real slot (so move it to the proper section in the header) and
3) set the proper signature for the slot.

Highly unlikely that normal users notice the runtime errors and
possibly unwantend behavior, as this all deals with the subtile GPS
service update threshold.

Signed-off-by: Jan Mulder <jlmulder@xs4all.nl>
This commit is contained in:
Jan Mulder 2018-09-24 10:00:55 +02:00 committed by Dirk Hohndel
parent b45124d554
commit fc812ea130
2 changed files with 2 additions and 2 deletions

View file

@ -39,7 +39,7 @@ GpsLocation::GpsLocation(void (*showMsgCB)(const char *), QObject *parent) :
loadFromStorage();
// register changes in time threshold
connect(qPrefLocationService::instance(), SIGNAL(qPrefLocationService::time_thresholdChanged()), this, SLOT(setGpsTimeThreshold(int seconds)));
connect(qPrefLocationService::instance(), SIGNAL(time_thresholdChanged(int)), this, SLOT(setGpsTimeThreshold(int)));
}
GpsLocation *GpsLocation::instance()

View file

@ -32,7 +32,6 @@ public:
int getGpsNum() const;
bool hasLocationsSource();
QString currentPosition();
void setGpsTimeThreshold(int seconds);
QMap<qint64, gpsTracker> currentGPSInfo() const;
@ -66,6 +65,7 @@ public slots:
void updateTimeout();
void positionSourceError(QGeoPositionInfoSource::Error error);
void postError(QNetworkReply::NetworkError error);
void setGpsTimeThreshold(int seconds);
#ifdef SUBSURFACE_MOBILE
void clearGpsData();
#endif