Tag #DHZ# yields "24" on my GW8

I will have to check this tomorrow night on my GW4. By the time I’d checked that I used the correct tag and that running the time up and then past midnight showed “00” as expected in Creator the real time here had moved to “01”

I’ve reported this to support.

Meantime it is a simple watch ( after I cleaned up all the artwork and made a duplicate of the gauge face from scratch ) so I’ll make a version to import in case this can’t be resolved easily by Facer.

2 Likes

Well argh, the GW8 switched to the AOD and I didn’t try again. The hour on the main face was showing 24 and the AOD screen uses the same #DHZ# tag.

Here you can see the Facer page display with 00, my GW4 with 00, and GW8 with 24.

No word from support. Must be really busy these days.

1 Like

No change. This has not been fixed yet.

00 means the start of a new day 24 means the end of the current day. So a train schedule might say - departs 23:50 arrives 00:20 next day. The ticket offic might say open from 06:00 to 24:00. So both are acceptable and can be used. However, 00 is more common. Ive come into this conversation late but if Facer gives no choice then it should be fixed as a bug, if there is a choice then its not a bug
I must admit though that the same tag produces a different result on different watches is a bit strange. I suspect it may not be just a Facer question.

1 Like

I have only only two things to say .
.
#DHZ# #DkZ#
.

The tag says range is 00-23. It yields different results on different versions of WearOS.

1 Like

I think they are trying to stop us using Tags with Z in them . I think it might be worth trying the hard coded leading zero . It is a bit of a pain ay first but then it is a copy and paste exersize . I like the way the Tags list is Active right now .
.