Watchface : Is it possible to detect preferred formatting?

I have a watch face, that displays distance. Is there a way to know whether the user prefer miles or KM so I can display the appropriate type?

Also how can I detect if they prefer the date as MM/DD/YY or DD/MM/YY?

We need a way to make a call to find out the device config for these settings so we can display accordingly. Sorry if there are flags already for this, couldn't find them.

Thanks.
  • I have a watch face, that displays distance. Is there a way to know whether the user prefer miles or KM so I can display the appropriate type?


    Have a look at System.getDeviceSettings().distanceUnits

    Also how can I detect if they prefer the date as MM/DD/YY or DD/MM/YY?


    Nothing for this just yet... For now, we just use is24Hour - that almost match :D
  • Have a look at System.getDeviceSettings().distanceUnits

    Nothing for this just yet... For now, we just use is24Hour - that almost match :D


    Thanks. We need to be able to detect what format the date should be displayed in. Garmin please add this. Ta
  • @RUPERHAWKES I checked into the date format, and right now there's no user-configurable date format on our devices. In Garmin Connect and Garmin Connect Mobile you can set a date format preference, but that does not propagate to devices. Adding a date format option would be something that would have to be done at the system level by our device teams. If it became available, then we could add support for that setting in the Connect IQ API.
  • So that means I have to have a US version of my watch face AND a non US version of my watch face. Do you realise how cluttered your own app store will become because of this?

    Imagine I have a black on white and a white on black version of my watch face (due to your own limitations of watch face user configurability) so now we have for a single watch face the need for 4 versions of it on your app store. It will get cluttered and messy very very quickly.

    This is something you need to address else you will be overrun!
  • No, this does not mean that you have to have a US version and a non-US version. All it means is that you need to use the resources system; this stuff is covered in the programmer's guide, and I mention how you can do it here...

    Don't swamp the app store with multiple versions of the same app. There are, or will be, ways to get what you want soon. If you want to be able to support multiple colors for watch faces, the App properties system that is supposed to be part of the next release will allow the user choose. If you want a device-specific color scheme (use red for the Fenix3 and blue fore the 920XT), you can use the resources system. Simply define a string in a device specific resource file, and provide different values for each device.
  • Thanks, but that relies on the language. Is that how the device decides to format the date, i.e. based on language?

    Also you you know when the app properties API will be available? I'd like to allow the user to configure the watch face themselves too.
  • The solution Travis is providing is based on language, but it's not a function of the device. It's just a way to use the resource compiler to format the date based on the language setting. :)

    I don't have a time frame for the app properties API, but I can confirm that it's something we're working toward. We appreciate your patience!