Need help with new tags for WFF compliance

Facer Creator
1

I make pretty simple watchfaces, date, time , steps, watch battery percentage, phone battery percentage plus of course an image of some kind .
I figured out how to change the date tag to make it compliant. Have no clue how to do the battery tag changes for phone and watch. Hoping someone can help me.
Thanks!
Jrosy

2 Likes
2

You should check the Topics covering This stuff already. The current situation is no Phone bsttery and Watch battery progress only . The situation is changin all the time because Creator WFF is in Beta . Thingscould change Daily . Enjoy .

3 Likes
3

thanks

2 Likes
4

Look at this .
.

1 Like
5

Nice resource @russellcresser

Certainly goes to show exactly how much WFF cannot do in comparison.
I refuse to believe they do not have date/hour/minute functions with no leading zero though, if there is no pad() function.
Only just back but I am assuming these are ones that are still work in progress to translate to the WFF equivalent.

Also, with ‘Not supported in this format. Default value will be used’, this begs 2 questions:

  • Will there be a format in which it is supported at some point?
  • The default value for what?

There has certainly been a metric F-ton of work done here while I have been away though and I applaud the gargantuan effort to get this far.

2 Likes
6

@Facer_Official
We definitely need one of these for functions since floor() seems to be fine but ceil() throws an error. Who has one without the other?
Thanks @personNotToBeSwampedWithTestingRequests

1 Like
7

Perhaps get a ticket on it . I will not . I am concentrating on the WFS bugs . You might find it fixed one morning . Sorry to dissaper the lights are out here .

1 Like
8

What type of bugs does WFS have?

2 Likes
9

The recent update with two new Utilities , multi Preset and Image Swap , are supposed to elevate the Face to SDK 36 but hold the Faces in Revew when published on Google Store .
For example . Best to check the WFS Forum for Detail .

1 Like
10

Thanks for the info. This has been the buggiest past few months ever - everywhere!

2 Likes
11

My Son in law visiting Just got an Ultra ( not my Fault ) form a local Retailer . Not long ago We Called them GW7 Ultra . Now we also Have a GW Ultra ( 2025 ) . So now the named Ultra costs say £250 ( we got some discount ) and Ultra ( 2025 ) costs £500+ . Both have the same Model number ( well done Samsung ) . So the 2025 comes with WOS6 out the box and the ( 7 ) Ultra updated in the first hour of the watch being connected to Wi-Fi . So right now we are both Playing with WFF . No Going back Now .

1 Like
12

Come back…come back

2 Likes
13

My bad. They are there, for some reason mine wasn’t scrolling that far earlier. I do notice that floor is included in this list but not ceil though so maybe the conversion just has not been implemented yet.

1 Like
14

So, For my battery depletion that used (212-(212/100*ceil(#BLN#/10)*10)) I can instead use (212-(212/100*-floor(-#BLN#/10)*10))

Just in case anyone wants a WFF compliant one before ceil() gets implemented

2 Likes
15

Here’s a fully compliant 12/24 time string too (untested in WFF but fills the leadings correctly):
$#DTIMEFORMAT#==12&&#Db#<10?" ":$$#DTIMEFORMAT#==24&&#Db#<10?0:$#Db#:$#Dm#<10?0:$#Dm#

OK, I’ve tested all these as working as previously but should do the leading zero for WFF.
Most folks will have these already but thought it would be good to pull them all together for someone just coming back and reading the thread.

Full Time
$#DTIMEFORMAT#==12&&#Db#<10?" ":$$#DTIMEFORMAT#==24&&#Db#<10?0:$#Db#:$#Dm#<10?0:$#Dm#
Hour
$#DTIMEFORMAT#==12&&#Db#<10?" ":$$#DTIMEFORMAT#==24&&#Db#<10?0:$#Db#
Minute
$#Dm#<10?0:$#Dm#
Hour Left
$#DTIMEFORMAT#==24?floor(#Db#/10):$$#DTIMEFORMAT#==12&&#Db#>9?1:$
Hour Right
(#Db#%10)
Minute Left
(floor(#Dm#/10))
Minute Right
(#Dm#%10)

1 Like