i tried using this tag to turn text on and off ([IS_DST]==0?100:0), mostly for my timezone (EST/EDT)
when i run it in wfs it changes with the calendar accordingly. i was expecting to see the change this weekend on the watch 5. however, none of my watch faces using this tag showed any change. again, it worked as intended in the run window so i was expecting it to work the same on the watch. am i missing something?
Also, on an unrelated note, as of yesterday all of my watch face complications in galaxy wearable stopped allowing me to edit any of my complications. they all show none for the options. i tried googling the issue but the best i could find was a reddit article saying it fixed itself on itâs own. anyone else come across this? (fwiw: yes, they are still editable on the watch itself)
so i was expecting it to work the same on the watch. am i missing something?
Did you change your tag for EST text box to (([IS_DST] == 1) ? 0 : 100)
It may be that your âSystemâ only shows DST when it is on and doesnât report it as off. You can report this as a bug if you like.
Also, on an unrelated note, as of yesterday all of my watch face complications in galaxy wearable stopped allowing me to edit any of my complications.
This happens a lot with my favorite MD watch face. I think it is the wearable app because you can still modify them on the watch. I think restarting the wearable app or the watch fixes it.
Let us know if those have an effect since mine hangs up often Iâll see what needs to be done. I know just switching to a different watch face and back does not resolve it.
these are the way i wrote out the tags:
([IS_DST]==0?100:0) for standard time
([IS_DST]==1?100:0) for daylight time
these codes work fine in the run window.
for the complications, iâve tried rebooting both the phone and the watch, even went into the app settings and cleared the cache for both wearable and manager. all to no avail. and yes, all of my watch faces are effected, so just switching back and forth has done nothing for me as well.
I know
what do you get if instead of opacity you have a text box that has this
(([IS_DST]) ? âDSTâ : âESTâ)
That only depends on the existence of DST and not this being a zero number.
for the complications, iâve tried rebooting both the phone and the watch, even went into the app settings and cleared the cache for both wearable and manager. all to no avail. and yes, all of my watch faces are effected, so just switching back and forth has done nothing for me as well.
The issues Iâve seen only affect setting on the Wearable app and you can still set them on your watch. Can you change the factory installed watch face complications. If That is your case you might try uninstalling and reinstalling the Wearable App.
And yes the ones I saw on Redit all say it came back but they were older posts.
@r.liechty_SDR
getting away from EST for a moment,
i was able to change factory installed watch face complications so i went ahead and uninstalled and reinstalled wearable. reset the phone and reconnected the watch. still saying no comps on my personally made watch faces.
@Knightwing
first i set the opacity levels to 0, then enter my tags. it doesnât show up in the work window but will in the run window. and the way i have the tags written, it works fine in the run window and views fine on the watch. only problem was with daylight savings ending this past weekend i expected my text boxes to switch from EDT to EST as it does in the run window. i use these tags in several of my watch faces and they all had the same negative result.
@Knightwing
i donât think itâs the brackets. i donât think it has anything to do with the tag. it views fine in the run window. i think @r.liechty_SDR was on to something:
every way i try to write this code it still doesnât show on the watch like it does on the computer.
If not, can you use ron method instead?
Or do some troubleshooting i.e just
[IS_DST] in text box.
That will display values 1 or 0 like in my screenshots.
If it changes then something wrong with tag expression or layers opacity settings not being reflected for some reason.
If this a case , u could create a 0% opacity text and a 100% opacity text to see this works.
If its remains the same.
Then u know [IS_DST] not working. (Doubt it, could be settings on your phone DST is not reflected)
In my screenshots i used
([IS_DST]==0)?100:0
Didnt test without brackets.
Anyway if u can wait. I can create wfs file and upload it here next monday.
U can use that as a sample , load to watch see if it works
thank you @Knightwing
i started a new face from scratch and only put 1 text box in the center. when i entered [IS_DST] alone my watch face returns a 1. tried it with ([IS_DST]) and same result. it shows a 1 on the watch when the run window correctly shows a zero for todayâs date with and without the parenthesis.
if i put the parenthesis before the question mark however it does not like that in wfs, the text box just shows everything after the closing parenthesis starting with the question mark.
this one is correct. i wasnât having a problem with syntax. for a simple enough tagline you shouldnât need all those brackets, itâs nothing compound. it shows multiple ways correctly (with and without extra brackets) on the computer screen just not when i put it on my phone.
i checked all the phone settings and by default the time zone is determined by my carrier. another option is to use my location to determine the timezone, but iâm in the same spot so that didnât make a difference.
perhaps this is an american issue as most of the world doesnât use daylight savings?
