Add 'location_t' data structure

Instead of having people treat latitude and longitude as separate
things, just add a 'location_t' data structure that contains both.

Almost all cases want to always act on them together.

This is really just prep-work for adding a few more locations that we
track: I want to add a entry/exit location to each dive (independent of
the dive site) because of how the Garmin Descent gives us the
information (and hopefully, some day, other dive computers too).

Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

1 files changed, 3 insertions, 3 deletions

diff --git a/qt-models/divelocationmodel.h b/qt-models/divelocationmodel.h
index fe78854b9..14077609c 100644
--- a/qt-models/divelocationmodel.h
+++ b/qt-models/divelocationmodel.h
@@ -38,12 +38,12 @@ class GPSLocationInformationModel : public QSortFilterProxyModel {
 Q_OBJECT
 private:
 	uint32_t ignoreUuid;
-	degrees_t latitude, longitude;
+	location_t location;
 	bool filterAcceptsRow(int sourceRow, const QModelIndex &source_parent) const override;
 public:
 	GPSLocationInformationModel(QObject *parent = nullptr);
-	void set(uint32_t ignoreUuid, degrees_t latitude, degrees_t longitude);
-	void setCoordinates(degrees_t latitude, degrees_t longitude);
+	void set(uint32_t ignoreUuid, const location_t &);
+	void setCoordinates(const location_t &);
 };
 
 class GeoReferencingOptionsModel : public QStringListModel {