What is going on here? I thought I covered everything. I even tried a complete redo.
and yet…
1 Like
What I saw:
- You are using the pad function. It is not supported.
- “cdt 12” has 2 fields with formulas, that might be a stumbling stone.
4 Likes
I haven’t looked into it, but maybe with 2 elements, so one with a 0 in front, like:
0(11-(#DH#%12)))
3 Likes
Here is how I do almost all of my time displays and they will always show leading zeros for the hours. It also passes the WFF conversion test. I picked this up years ago here in the community posted by @phelanengland
Hours:
(0-2) (floor(#Db#/10)) Dim 12h $#Db#<10&&#DTIMEFORMAT#==12?10:100$
(0-9) (#Db#%10)
Minute:
(0-5) (floor(#Dm#/10))
(0-9) (#Dm#%10)
Seconds:
(0-5) (floor(#Ds#/10))
(0-9) (#Ds#%10)
6 Likes
Thanks for the input, I appreciate it 
3 Likes
Thanks for the heads up guys 
Not sure why it’s showing unavailable though, usually have an option to Preview Premium Faces but not for this one…unless the Preview option has changed recently 
1 Like
I think it was not published for WOS6 / WFF .
2 Likes
It was not published for WFF.
2 Likes
I tried that with a conditional, but it still fails. ie if<10 0(#value#)
3 Likes
Yeah . I think in the text box we have to use floor and % then do our conditional stuff in the Position or Opacity Field . Sorry I have lost track a bit . I am mostly importing ABB these days .
2 Likes
It’s all double dutch to me 
5 Likes
As @russellcresser hinted, there are now more limitations of what coding can be done in the fields.
Maybe this thread helps:
4 Likes
Blimey . That is going back to Day One . Nice one Tom .
2 Likes
I’ll check that when I get back to my pc! Thanks
3 Likes
Hi, this has changed with the WFF compliant code. The Facer parser now requires simplified WFF code. For a countdown, you can use the following simple code in the text box:
(23-#DH#):(59-#Dm#):(60-#Ds#)
3 Likes
Silly me. I had one that passed the test, and didn’t realize it 
This is inspectable. Thanks for the support all 
2 Likes