mirror of
https://github.com/subsurface/subsurface.git
synced 2025-02-19 22:16:15 +00:00
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>
This commit is contained in:
parent
c986940630
commit
28e3413ff6
40 changed files with 251 additions and 264 deletions
|
@ -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 {
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue