I have made a couple of watchfaces using graphics instead of numbers where if the user selected 12 hours format it would show nonsense. Is it possible to force only the 24 hour format with leading zero? I must admit I’ve read posts here but I am still confused and any clarification is welcome.

I will switch on my PC and have a look at the Tags . It should be possible .

So @BIELITZ . Will it only be nonsense after 12 if the 12 hrs clock is selected . #Da# tells you if it is afternoon .

If you use #DHZ# or #DkZ# for your hours it will always only be 24 hrs lading zero .

Only if you use #Db# or #DbZ# ( leading zero ) will you get the option to User set it 12/24 .

Phew - thanks for the info!

Will that Do it ?

I think so- I’m not at my pc so i will try later but thanks again!

Let us see what you are doing or DM me . Sounds Great .

This watchface is an example of what I mean - in Creator the time slider seems only to work in 12 hour format. The graphical numbers I am talking about in this case arr the flag men.

Ah Yes . Man Overboard . I can not pretend to understand the Semaphore but the slider works fine for me on inspection . Are you on a Windows PC ?

Normally yes - but today I am only on my mobile.

Just out of Interest .

.

`$((#Dm#)%10)=2?100:0$`

.

Does the same Job for the Minute Units as

.

`$(#Dm#-((floor(#Dm#/10))*10))=2?100:0$`

.

I see that the Hours A B options only work with the Z options .

It seems to all be working to me .

The timeline Slider is only ever 24 hrs for the whole day .

You are of course correct - the slider is 24 hours but what I really meant was the clock that accompanies the slider

Yeah . Shit isn’t it . While you are developing stick in a Test Number Layer showing #DH# .

Oh wow - that makes it easier! Now why didn’t I think about that instead of struggling

Yes . Follow Peter wherever he goes . My developments have loads of test Layers all over the place . My favourite for simulation is #DWFHS# which gives you a nice slider without having to open the settings .

I’m useless with this modulo stuff but I think that I’ve cracked it now …

First thing that I realised was I’m dealing with ‘digits’ and not numbers so say it’s 13:12pm

#Dm# is minutes in hour and equals 12 in this case

% = modulo or mod so -

$((#Dm#)%10)=2?100:0$ becomes:

$((12)%10)=2?100:0$ becomes

12 mod 10=2? If yes 100 if no 0

Mod = the remainder’s first digit of the answer so-

Digit of the remainder of 12÷10 =2 if yes 100 if no 0

12÷10 = 1.2 the remainder equals 2 ie the digit is 2 therefore we now have-

$(2)=2?100:0$ ie the condition is true and the result is 100

To clarify modulo a bit more (from Wikipedia) **“5 mod 2” evaluates to 1** , because 5 divided by 2 has a quotient of 2 and a remainder of 1, while “9 mod 3” would evaluate to 0, because 9 divided by 3 has a quotient of 3 and a remainder of 0.

So that’s my understanding - if I’m wrong please help me understand

Yeah You seem to have a good handle on Modulo . I am not very good with terminology as remembering names is a bit of a problem for me . For me the Face is full of tests till it is working properly . I have about 1500 faces in my profile 255 are Published . The others are tests and WIP .

I think modulo was explained here on forum several times, I somewhere wrote it like this:

remember when you learned division of numbers before you learned decimals? There was a/b meaning how many times the whole b can be subtracted from a and how much reminds of it after that. This reminder is what [tag]%x gives, like no mater how many times you can subtract whole x from the tag, main thing is what reminds after that.

In case of #Dm# we are inspecting the second digit, which can go from 0 to 10, that is why there is %10.

You are right - but now I understand!