Thank you.
However, if the development team supports WFS as a basic tag, it will not be necessary to consider the calculation formula complexly every time.
It Step Count over 100% isnât in the upcoming hotfix, Iâll add it as a suggestion for the next update.
Ron
Samsung Developer Relations
Support for otf fonts.
Can there be added support for .svg images? It would allow to have all elements crystal clear sharp at any size and device display resolution with small file sizes.
I doubt it it isnât a supported Android media format but I can request it.
Ron
I can request it but Fonts are heavily copyright protected, they usually require license, hard to review, etc.
I could not find a list of applicable font types in Android Docs but if you can find them and they are available for Android then they should be for Wearables as well.
Ron
Samsung Developer Relations
I second this one. An efficient way to store data and always have the best quality at any size.
Ok, thanks. I can create my own otf fonts in illustrator, using fontself, to create custom color font in the otf format.
Google alone encourages use of vector graphics namely .svg, but particular format is probably not that much important, I expect that before use they can be converted into whatever is supported.
It would be great to have a free-format ânotesâ field available.
As we develop watch faces and new versions are saved, it would be most useful to be able to make some notes, for example about what has changed in this version. There could be a button somewhere on the WFS workspace to open a notes window and allow text input.
The notes would only saved with the .wfs file and would not form part of the built watch.
I personally think it is virtually impossible for an individual to know if your work infringed on a font.
Ron
Samsung Developer Relations
Do you have any plans to support the Korean lunar calendar?
I didnât know it wasnât included. Iâll add it as a suggestion.
Ron
Samsung Developer Relations
Circular ProgressBar Range Setting Value Expression
Circular progressbar is based on 360 degree and so is its background color. Letâs say you want to create a battery meter that is 180 degree range instead of 360, then the range value expression would be [BATT_PER]/(360/180). But expression only applies to the progress bar, it leaves a 360 degree background color. If you want to use the background color, then youâll have to mask it off with additional image on top of it.
It would be great if Range Setting Value expression applies to both, the range and its background. thanks.
Hi X9
Progress bars are part of Wear OS system I donât know if WFS can modify them but I can ask.
You can use styles for the progress bar background or turn the opacity to zero.
Ron
Samsung Developer Relations
Yes, I agree, It would be good if there was possibility to adjust the arc range of circle that will be filled by 100% of the value range.
Meanwhile a simple workaround can be used. For example lets have battery bar, that has values from 0 to 100 and has to fill 1/2 of circle at 100%. Make the bar background fully transparent. Then set the value be 0+[BATT_PER]/2. Finally make a duplicate bar, move it below the first one, set the value to be 50 and colour and opacity to what ever you like for a background.
Edit: can anybody tell me why the end of background bar behaves like this?
I attached my example file, do not extract just rename to .wfs
SecXpl.zip (606.1 KB)
Hi Peter, for me itâs working fine on preview.
Maybe you using the Mac makes the difference. I am sorry for putting this here, but it only illustrates, that the workaround may not fully solve missing feature.
Whenever I put the background arc to 50% it shows crooked end when set to flat cap style.
I am using Windows PC
Do you work with Macos? I work with MacOS and it is displayed