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
|
@ -108,7 +108,7 @@ QString DiveObjectHelper::location() const
|
|||
QString DiveObjectHelper::gps() const
|
||||
{
|
||||
struct dive_site *ds = get_dive_site_by_uuid(m_dive->dive_site_uuid);
|
||||
return ds ? QString(printGPSCoords(ds->latitude.udeg, ds->longitude.udeg)) : QString();
|
||||
return ds ? QString(printGPSCoords(&ds->location)) : QString();
|
||||
}
|
||||
|
||||
QString DiveObjectHelper::gps_decimal() const
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue