I can’t seem to get $#DkT#==twenty one?100:0$ to work ie show an image of the number 21. It seems to be a problem that there are two words even though the result of #DkT# is two words. $#DkT#==twenty?100:0$ however does work. Anybody can give me a hint please?
2 Likes
Why can you not just use $#Dk#==21?100:0$ ?
2 Likes
I’m using coloured images of the numbers in - this case a gold 21
3 Likes
$#Dk#==21?100:0$ in your opacity will light it at 21:00 . I am surprised The conditional handles a string at all . Obviously they have not sorted out the strings with spaces .
2 Likes
Most of the time for Opacity you have to use a number instead of a word. The only exception I can think of offhand is the daytime vs nighttime and it’s a true false.
3 Likes
#Dk#, #Db# don’t work for me- so I must be doing something wrong somewhere. I’ve left #DkT# for 0 to twenty so you cas see that my conditional works (partly)
3 Likes
2 Likes
Ha . I see . If Basic tags don’t work we are Buggered . Sorry I will have a look at your WIP in a bit . Have you tried another Browser ?
Try using
$#DH#==21?100:0$
I think #Db# is a special case that can not be used in Conditionals . Sone times it a]can be 12 HRS sometimes 24 . 
1 Like
No luck with #DH#
1 Like
You cant expect them to light up by tag expression, when you shut the eye on them
3 Likes
As a side note, even if you do get it all figured out so that the numbers show correctly, it WILL NOT be WFF compliant. I’ve done a few pictures for time display faces and none of them will pass the test for WFF even if Facer Creator shows no issues and shows WFF being OK. They will always fail on the final conversion when you publish it.
2 Likes
You could be right there! Oh dear!
3 Likes
I can hope that in the next few years or so, Facer will fix it.
3 Likes
It just published! It’s in my watchbox and live! Maybe one of you could check and see if it is live for everyone…BLZ-XXX Digital Gold test
3 Likes
Basic rule of thumb is that you can use a numeric equality test to produce a string result option but you cannot use a string based equality test to produce a numerical result option.
In addition, when working with numbers only, it is often better not so use the $ qualifier so use (1==1?100:0) instead of $1==1?100:0$
It does mean you have to remember when $expression$ is absolutely required (when any part uses a non numeric as input or output) but purely numerical conditions give you much more flexibility on nesting and multiple equality tests.
2 Likes
Thanks for bringing this up!
If you’re still running into this issue or any other problem with Creator, we’d really appreciate it if you could open a support ticket here:
https://help.facer.io/hc/en-us/requests/new
Submitting a ticket helps our team track issues more closely, share them with the right people, and start the internal discussions needed to work toward a fix. Every report helps us make Facer better for everyone!
1 Like