3 Commits

Author	SHA1	Message	Date
Gordon Williams	b2aa61e182	Changed NavigationSpec's distance into a String. ... Previously we used an integer (in meters) but when using Google Maps navigation, Google Maps picks units based on locale *and* the distance - it might report "100m" or "20km". Then we carefully undo all that work, and for PineTime we just as "m" so you may well have "20000m" or more displayed, which is not ideal. I imagine at some point that will change, but we probably want to be able to handle that in the OSMAnd side of Gadgetbridge so all watches that implement navigation will benefit (and won't duplicate code).	2023-06-13 07:32:12 +00:00
Gordon Williams	1fa8936544	Google Maps: Added more recognised icons - needed another enum for going all the way around a roundabout	2023-06-09 13:59:05 +01:00
Gordon Williams	735f27d5bf	Add Navigation handling to Bangle.js ... Add extra 'ETA' field to NavigationInfoSpec Allow Local Notifications from Google Maps to be parsed into NavigationInfoSpec by GoogleMapsNotificationHandler Moved notification handling after blacklist check as per https://codeberg.org/Freeyourgadget/Gadgetbridge/pulls/3136#issuecomment-920095 Ensure we don't create a nav message for 'Location Shared with you' messages. Recognise 'ft' as a distance unit and convert accordingly Google Maps navigation: Adding new recognised icons, and removing warnings/errors from file	2023-06-09 08:50:40 +01:00