Here we go again, not being able to publish a face again. 
3 Likes
Yikes! Thatās no fun. I take it that your design has some sort of animation sequence in it? Iāve honestly not really looked into what WFF supports since my work is relatively basic and is for the most part compatible with WFF (so, I apologize if my assumptions are off).
2 Likes
I got it fixed. It didnāt like this code:
$#Dd#>=4&&#Dd#<=12?#Dd#th:$$#Dd#>=13&&#Dd#<=20?#Dd#th:$$#Dd#>=24&&#Dd#<=30?#Dd#th:$$#Dd#==1?#Dd#st:$$#Dd#==2?#Dd#nd:$$#Dd#==3?#Dd#rd:$$#Dd#==21?#Dd#st:$$#Dd#==22?#Dd#nd:$$#Dd#==23?#Dd#rd:$$#Dd#==31?#Dd#st:$
3 Likes
Glad you could figure out what didnāt belong in that chain of code. To me it looks like when a toddler starts punching random characters on a keyboard (just kidding)!
2 Likes
LOL that was my code! SORRY What did you use instead? I havenāt used that one in a while .myself
2 Likes
Used the default
1 Like
Went to publish another one with a custom font and it did not publish, so, I put all the text to a default font and still didnāt publish!!! So, I take it weāre back to square one on this publishing shit again!!! All this crap is getting so fricking annoying!!!
Someone want to see if they see something wrong with this face?
Youāre not by any chance using the Beta testing version of Facer Creator, are you? Iāve published several watchfaces within the past couple days, all with imported fonts like yours, and theyāve gone through the publishing process just fine.
I used to be signed in as part of the Beta Testing group, but I pulled out after I felt like it was causing issues publishing new designs.
2 Likes
Nope, Iām not using the Beta
1 Like
(post deleted by author)
Using āStrokeā perhaps?
3 Likes
Quote:
So, I take it weāre back to square one on this publishing shit again!!! All this crap is getting so fricking annoying!!!
I removed my suggestion about stroke and glow. If I had not missed the the colorful language when I went through this discussion thread, I would not have bothered to reply.
Iāve published fine in WFF with Stroke and Glow. But you have a weather layer with conditionals in the text field. Conditionals work in X/Y and opacity fields but canāt use them in text fields for WFF. Thatās likely the problem. The workaround is multiple layers with the conditional in opacity field instead.
1 Like
So we canāt use a weather string like this anymore?
$#WCCI#==01?Clear:$$#WCCI#==02?Few:$$#WCCI#==03?Scatter:$$#WCCI#==04?Cloudy:$$#WCCI#==09?Shower:$$#WCCI#==10?Rain:$$#WCCI#==11?Storm:$$#WCCI#==13?Snow:$$#WCCI#==50?Mist:$
From my experience, this kind of functions no longer works because the new Facer/WFF parser doesnāt support overly complex nested conditional expressions anymore. You can fix this by using separate layers for each value and controlling their opacity (e.g. $#WCCI#==01?100:0$ ). One large all-in-one formula is now considered too complex and gets rejected. Sometimes you can split it up in two formulas.
2 Likes
no you canāt use ANY conditionals in the text field. Youāve got to accomplish any such things with multiple layers and conditionals elsewhere. More WFF BS
3 Likes
Yes, youāre right. I just tested this simple formula in a text field:
$#BLN#<20?āLowā:āOkā$
Itās not accepted for WFF, even though it works fine in the Creator and on the watch app, and even shows a green compatibility flag in the Creator.
1 Like
yeah this is something weāve discussed for a bit now after learning the hard way 
2 Likes