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
|
@ -109,16 +109,16 @@ void MapWidget::selectedDivesChanged(QList<int> list)
|
|||
skipReload = false;
|
||||
}
|
||||
|
||||
void MapWidget::coordinatesChangedLocal(degrees_t latitude, degrees_t longitude)
|
||||
void MapWidget::coordinatesChangedLocal(const location_t &location)
|
||||
{
|
||||
CHECK_IS_READY_RETURN_VOID();
|
||||
emit coordinatesChanged(latitude, longitude);
|
||||
emit coordinatesChanged(location);
|
||||
}
|
||||
|
||||
void MapWidget::updateDiveSiteCoordinates(uint32_t uuid, degrees_t latitude, degrees_t longitude)
|
||||
void MapWidget::updateDiveSiteCoordinates(uint32_t uuid, const location_t &location)
|
||||
{
|
||||
CHECK_IS_READY_RETURN_VOID();
|
||||
m_mapHelper->updateDiveSiteCoordinates(uuid, latitude, longitude);
|
||||
m_mapHelper->updateDiveSiteCoordinates(uuid, location);
|
||||
}
|
||||
|
||||
MapWidget::~MapWidget()
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue