This used to work, but doesn’t anymore.
$clamp(#DM##DdL##DHZ#,121908,121921)=#DM##DdL##DHZ#?100:0$
The point is, the picture is showing on the 12/19 between 08(am) to 21 (9pm). Or what could be the alternative? I’ve used this in so many of my watchfaces, and now they are useless
Looks like Voodo to me. But in my experiance you can not do maths with numbers with Leading Zeroes. Facer has had to change the way Formulas work to get all the Operating systems in a line.
I will have a look at your Formula when I get on my PC. I can not imagine what it is supposed to do at the moment.
Post an Inspectable Link here so we can see how you are trying to use it.
If you are wanting to show a picture on only one day Dec 19 and only from 8 am until 9pm I would use $#DMM#==12&&#DdL#==19?160:999$ in either the x or y box and $#DH#>7&&#DH#<21?100:0$ in the opacity box. I’ve found it simpler on my brain to split complex expressions into two or three different expressions in different boxes. “Whenever possible”!
No, you are probably correct, but the DH tag is not a leading zero tag. According to the tag page it’s 0-23 in operation. I believe DHZ is the leading zero version with 00-23.
In a different watchface, I figure this extended formula out in the meantime:
$#DOW#!=5?0:(#Dk#!=8?0:(#Dw#=45?100:0))$
So maybe if I use the true/not true together with equal/not equal together with “Is equal to”/“not equal to”. It could be successful. Or else I do the simple solution mrantisocialguy wrote.
Personally, I would not trust that this will function in every watch brand. What I’ve noticed from experience, if any brand of watch will break an expression it’s TicWatch. Also really old versions of WearOS are very picky about how code is written. Doing that same expression for myself if I wanted a picture to show on Friday at 08:00 to 08:59 on the 45 week of the year, I would use this.
X Box $#DOW#==5&&#Dk#==8?160:999$ and Y Box $#Dw#==45?160:999$
But you must understand, I’ve posted stuff that works perfect in Facer Creator only to have it bite me in the butt after being published and in the real world. That is why I use a Fossil Carlyle 5th gen as a dedicated test watch that everything I publish has been synced to and fully tested.
I agree with you, and also learn by your experience. Keep it simple, is the way. So I will use the X and Y box much more, instead only the “opacity”-box.
Thanks for your advice
@to.et.ni I see you have used this structure of code in many locations in the face above .
What you have to do is ensure that a line of code works before you copy and paste it everywhere . You do not have to Manifest / Disappear every Tag Box .
You can decide to do it with Opacity . Size or Position . You don’t have to do all three.
I am sorry but it is not obvious to me what the Formula is supposed to do .
Get something simple working then Expand your Face to suit .
You are also not limited to just the X, Y and Opacity boxes either. You can also use Width and Height to set something at zero width or height when you don’t want it to be seen. You can also use all of the above plus font size in the text element to make the font size zero when you don’t want it seen. There are lots of options if you think outside of the box.
I was going to say the same thing until I scrolled down and discovered that you had already said it. Yes, it seems that simple coding seems to work for a longer period of time after Facer makes all kinds of changes and updates to the app. It can be a pain to go back and try to find everything that needs to be redone if something stops working.
I’ve been going though that this morning. I just finished updating 38 holiday watchfaces that I had used the Stroke or Glow effect in before I learned that WearOS doesn’t play nicely with it.
Been there/done that with the Stroke.
… and Facer is going to have a lot of useless Happy New Year 2023 watch faces if people have done a Google Image copy/paste instead of having the year change for the future.