I’ve got a few watch faces that I created which don’t properly show the hours in the watch face preview in the android app when in the 12 hour clock mode, however they work fine on my Samsung Galaxy watch. They don’t show well in the browser creator app, but it bogs down so much I don’t expect it to.
These watch faces which don’t show the hours in the android app while in 12 hour clock mode, all have in common two things.
- They use an animated font for the clock.
- The hours digits undergo a check for 12 or 24 hour time format so it will know what digits to display. The ten’s hour digits use the following expression for a check in the x coordinate:
‘$(floor(#Db#/10))==1?60:2000$’
for in this case the digit 1.
The one’s hour digits use the following expression for a check in the x coordinate:
‘$#DTIMEFORMAT#=12&&#DhZB#==1?110:$$#DTIMEFORMAT#=24&&(#Db#-(10*floor(#Db#/10)))==1?110:2000$’
for in this case the digit 1.
I understand these formulas are a bit outside the box, but they are necessary to maintain compatibility to both 12 hour and 24 hour clock modes for animated fonts using sequences and coordinate substitution for the digits. Unfortunately transparency is not supported for sequences.
The watch faces of mine that this bug affects are (must wait quite a while for them to load fully):
The animated font itself is definitely not the problem, because the watch faces that I haven’t converted to dual 12 / 24 hour time compatibility display just fine in the android app preview. These are:
Also, the formula’s noted in 1 & 2 are not the problem themselves, as they are implemented in another watch face of mine without animated fonts, and the clock in both 12 & 24 hour mode shows up fine in the android app for this face.
Is it simply the processing power of the phone? I have a hard time believing that as my Samsung S10+ phone is many times more powerfull than the Galaxy watch. Any way, I think it might be a bug and I thought I’d report it.
Thanks.