Feature request: time/date engine (aka 'black box')

Feature Requests Tags & Functions in Facer Creator
11

I just modificated your text base formula into rotation by adding rotation angle. That does the trick but it only works for 12h, the other 12h the hand stays on the 12 o´clock position.

((floor(#DNOW#/3.6e6)%24)<10?0(floor(#DNOW#/3.6e6)%24):(floor(#DNOW#/3.6e6)%24)*(360/12))

What i need is a UTC based rotating hour hand that can be modified with #VAR# decrement and increment (-1/+1), choosing the timezone, beginning at GMT/UTC.

Formula for #VAR#-rotation in angle steps could be made by: * (#VAR_1# * -15).

12

That’s the ‘presentation’ formula, and includes ‘leading zero’ logic.

You want something like:

((((#DUHZ#+2)/12)+(#DUmZ#/720))*360)

And substituting (for ‘+2’), I suggest:

(((((#DUHZ#+#VAR_1#)/12)+(#DUmZ#/720))*360)%360)

1 Like
13

This looks nice but it´s working in the wrong direction.

But when i choose - instead of + it doesn´t work with -1, -2 …

(((((#DUHZ#-#VAR_1#)/12)+(#DUmZ#/720))*360)%360)

1 Like
14

Try this:

(((((#DUHZ#+(#VAR_1#*-1))/12)+(#DUmZ#/720))*360)%360)

1 Like
15

That´s it! Nice! You´re my superhero of the day!!

16

That´s what it looks like now. Press left or right on the WT-bevel, Above for reset to UTC 0.

1 Like
17

You may also need wrap-around logic, as your +/- variable is open-ended.

I suggest this:

(((((#DUHZ#+((#VAR_1#%12)*-1))/12)+(#DUmZ#/720))*360)%360)

1 Like
18

True! Thank you very much for your help. Now i know that it is 8 pm in Sydney. :wink:

Mission World timer accomplished.

I will mention you when the final watch face is ready.

19

@andrew.dowden, @GAUSS,
For sure this is tremendous math work well done! but I think you’re short one hour. Can you check on #DUHZ#?

I live in New York so as a quick litmus test I have my local time on the watch above and set the outer ring also to New York. The times should be identical but the zone 2 time is short one hour.

I just dropped an extra 1 on DUHZ to catch up… works through midnight on all zones.
((((((#DUHZ#+1)+((#VAR_1#%12)*-1))/12)+(#DUmZ#/720))*360)%360)

Can you verify? I’m using the edited formula above in a new watch.

Thanks,
John

1 Like
20

@jmorga106:

Can you confirm if ‘World Clocks v0.2’ (above) is correct for NYC (!?).

Note: It is set to Summer Time (EDT), and as yet has no logic for EST …

@jmorga106, OR @GAUSS,

What value is VAR_1 when ‘correct’ (on ‘World Timer test’) for NYC?

Note: I still don’t have access to new ‘Premium Designer’ #VAR# toys (or documentation), so was just (wildly) guessing.

21

that’s some pretty awesome guessing dude… Yes the daylight savings tracks correctly. Is it BST in UK? I know there’s a few week where they probably don’t match but by July they should track (London is +5)

-john

1 Like
22

@andrew.dowden, @GAUSS,

Wow this is getting really complicated. What if you wanted to also display the digital time as well - locally and in zone 2?
…aaaaaaaaaaand pad the leading zero(0) on 24-hour time?
…aaaaaaaaaaand what if the users can switch between 12 and 24 hour format?

I’m padding the lead zero(0) on 24-hour time like this: $#Db#<10||#Db#>=24?(0)#DK#:#Db#$

Premium designers must use the #Db# tag for hours on all designs to publish. Otherwise, Facer QA kicks them back.

The trick will be to modulus %12 on 12 hour time or modulus %24 on 24 hour time depending on user format. But there’s
no tag for that.

Still messing with some condition if #Db# goes over 12, then change the Modulus value, then add the #VAR_3# plus 1 to get to the ZONE 2 time. So if it is 10:14am in NY it should either be 3:14pm in London or 15:14 in London based on the user’s setting. How do I get myself wrapped up in these things??? :sweat_smile:

image.png731×1018 431 KB
1 Like
23

@andrew.dowden, @GAUSS,

Gawwwwwwwwwwwwwwwd… my brain hurts and it’s too complicated. I just did it with layers.

Scratch the below - my hours are moving in the wrong direction

scratch - So, ZONE2 hours is: (#DUHZ#+#VAR_3#+1)
scratch - but is only visible when hours are less than 24: $(#DUHZ#+#VAR_3#+1)<24?100:0$

scratch - the one case when the offset = 24 I’m showing double zeroes (00) as a separate text layer
scratch - shows when: $(#DUHZ#+#VAR_3#+1)=24?100:0$

scratch - the cases less than 10, I’m padding a spare zero (0) in front of the single hour number with another text layer:
scratch - shows when: $(#DUHZ#+#VAR_3#+1)<10?100:0$

I’LL FIGURE THIS OUT EVENTUALLY…

and then of course the minutes are just the regular #DmZ#

The hours and the extra zero layers are all left-justified.
The minutes (with colon : in front) is right-justified.
It’s all oriented so the colon : lands center-line.

I didn’t bother with 12-hour time for international zones. But the local time uses #Db# on hours.

I’ll finish this watch someday lol,
-john

1 Like
24

It is complicated with a load of variables.

That‘s why i only made a rotating bezel and hand depending on utc.

25

@jmorga106:

So, would you be in favour of a ‘black box’, embedded in Facer, that did most of this for you?

26

Surrrre if it’s not too much trouble. but I gotta figure this out. I’m close…

27

I tortured myself with the same formulae issues … before I just switch to using #DNOW#.

Once I had formulaic logic to return Year, Month, Day and Hours, Minutes from #DNOW#, it is easy to just adjust the time by +/- 1-13 hours. Then you just have to deal with Daylight/Summer Time start/end dates, etc.

My problem is that gets too complicated and has to be repeated 20-30 times in a single watchface …

1 Like
28

Hi Andrew, did you end up publishing your day and date solution for UTC? I can’t seem to find another person who was close.

29

I have made progress for UTC, and am still working on timezones (but making some progress).

Current thread: Select Timezone feature

Which showed this:

10%20-%20Active2%20-%2001%20(18-Jan)%20-%20UTC%20time
x49.10 - Active2 - 01 (18-Jan) - UTC time.jpg960×960 67.2 KB

3 Likes
30

Thanks Andrew
I’ve started a thread of my own, relating to my specific goal.