@ThaMattie . Now I remember seeing your work on this . So use the long Tags yeah .Cool . So much to Learn . Thanks for the heads up . I will make a Test .


@michaelavascarlet197 @ThaMattie If in Doubt Go for the Long Grunt . The Cheat is just a Maths joke but Hey HO . We are suppose to be having Fun . Thanks to Mattie who has been there for lots of People on Facer at Many Different Levels.

1 Like

Here’s an issue that you won’t know about unless you have more than one watch to test with. On sunrise & sunset tags, they force an am/pm display after the time. On sunrise24 & sunset24 they display correctly on WearOS, but on Tizen sunrise24 drops the leading zero on sunrise. Using wsunriseh & wsunseth forces a leading zero on WearOS with 12-hour preference but doesn’t with Tizen.

I have received complaints on all of these issues in the past. On the am/pm issue I get “I know the sun rises in the morning” type of complaints. On 12-hour preference I get a lot of “remove the zero” complaints. On 24-hour preference I get questioned about where the leading zero is at. (Tizen users only)

It seems to me that no matter what sun rise/set tag you use someone is going to complain about it.


Thanks MAG . I always thought that was what the 24hrs Clock was for . The Bus time tables for the Old Ladies down here are 24hrs no AM PM they seem to be there on time to get the Bus. Thanks for he heads up . Fortunately we are just switching stuff on and off at the moment. Good on Topic Stuff . As always when the Usual Suspects get involved The Topic becomes worth Bookmarking .


Yeah, I can imagine. I do not have any face (yet) that displays the actual times, but I use them in expressions to make graphical representations of day and night. Those always use the seperate hour and minute tags and the leading zero doesn’t matter there.

This could be solved in WearOS by adding parentheses. Anything in parentheses becomes a number, and numbers don’t display leading zero’s. For 24h you could then add the leading zero in the expression and it would work for both.

In fact, that will also work with “booleans”:
#DISDAYTIME#==true is the same as (#DISDAYTIME#)==1 (And I’ve actually used it without conditions by setting opacity to (#DISDAYTIME#)*100


Ha Ha I have ((#DISDAYTIME#)*100) in my test . Unfortunately I thought I discovered it . :::)))


Just tested this out:
Sunrise 12h


Sunrise 24h


Sunset 12h


Sunset 24h


They all displayed exactly correct for no leading zero on 12-hour and leading zeros on 24-hour selection on both my WearOS and Tizen watches. This is how I will be doing sunrise and sunset times from now on! One Big Thank You @ThaMattie !


Wow, another query post that has turned advanced tutorial. So much useful information here it needed to be bookmarked.

I just hope it isn’t information overload for @michaelavascarlet197 in his early days. There has certainly been a lot of grunting going on and thanks to all for the information and efforts involved in this.

1 Like

You are assuming the sun will always rise before 10am with this though :wink: In the reaaaaally nordic regions, it will end up as 010:29 like this. The 0 would need a <=9 check. Don’t know if there are sunsets before 10am, otherwise the sunset24 also needs a conditional leading zero.


That thought had crossed my mind. On the other hand, just how many people in those remote areas are going to care about the sunrise? Just for grins and giggles I checked online for today’s sunrise and sunset times in Qaanaaq Greenland. The website said, “Down all day”. Sounds like they need to know the sunrise and sunset weeks instead of hours and minutes. :laughing:



Thank everyone so much! I have learned so much. Creator is taking up all of my time in a good way!


UPDATE the color finally changed 7 hours after sunrise so it is making me think it might be something to do with a weather updating feature?

1 Like