Peter
January 20, 2022, 11:15pm
2
Hello. The offset tag provides text string, which cannot be used in calculation.
Hi,
I’m trying to make a reverse UTC lookup index for the UTC index in my watchface that works as a “decoder ring” to tell me what local-time hour corresponds to a given UTC-hour.
The gray is the local time wheel, it is supposed to rotate, but my tag-expression is not having any effect.
[image]
The tag expression I’m using: -[TMZN_OFS_WITH_DST]*15 (the math might be wrong, but that’s easy to check later).
This is what I want to happen if I am in, for example UTC-5, where local midnight is …
I would like to have 3 progressbar (battery) one over each other. the range of the first one is 0 to 20, second 21 to 80 et third 81 to 100.
so i put in color % the formula [BATT_PER] <=20? 100: 0 for a red color
the on second i put ([BATT_PER] >20) * ([BATT_PER] <=80) ? 100: 0 for white
and the last one going to be [BATT_PER] >81? 100: 0 for green.
the problem is that the red disapear when progressbar 2 (20 to80) appear
i want something like red white and green, and when the battery goes …
About the baro, you will be probably disappointed with the “WFS philosophy”
This is not the philosophy behind Wear OS Powered by Samsung (aka Wear OS 3) nor Watch Face Studio. See the**documentation on Complications **
The philosophy for WFS is to have a tool that designers can use to create Personalized Watch Faces with a standard user interface that is compatible with all Wear OS 3 devices.
As for barometric pressure and other sensor information. WFS may be able to access and create tags based on sensors. I can add Tags for Barometric pressure as a request but if…