When the face loads onto a watch it sets the phase but then cannot move. I found methods that worked better and did not need a spreadsheet to generate the expressions.
Here is that BTW, in case it is useful as a black box to check your number calculations:
3 Likes
Ah, cool, thanks! And … dang … this gave me an idea: Instead of the relatively bulky and inconvenient moon phase formula
(372-(((((#DNOW#+(#DOFST#*60000)-1739368380000)/1000)/3600)/(29.53059*24)-floor((((#DNOW#+(#DOFST#*60000)-1739368380000)/1000)/3600)/(29.53059*24)))*42))
for a “moon-shadow hand” rotation, I could as well take the #MOONAGEPERCENT# tag as basis. Which would really save formula space in the future. BUT: is #MOONAGEPERCENT# sync’d to the watch location? Or is it UTC-based? Can’t find info on that.
3 Likes
Others will know that better than I but I’m going to punt that it is location based as Facer is just using information provided by the watch OS and I’m pretty certain Google would have had complaints if their moon data only worked over their HQ, or Greenwich.
3 Likes
May be overthought on my side, stemming from working too much with #DNOW# which actually IS UTC-based. Thanks for the reasoning.
3 Likes
Yes. It’s the UNIX epoch I believe which is common for all languages.
3 Likes