Hi, so it seems that Watchmaker may no longer work on the latest samsung watches i.e. Ultra.
Does anyone know if the Watchmaker features can also be added to Watchface Studio?
I have faces that return variables from Tasker, {tvariablename} for example.
Is this also possible somehow on Watchface Studio, so I can run a Task, get a variable and then add that to my watchfaces?
Any ideas how?
I also have functions so that if the string.len is between x&y characters then the font would be for example size 20 and if its between a&b font size would be something else.
(basically so the text is not truncated when too long for the screen so it always fits).
Is this achievable in WFS?
Any help welcome!
Really dont want to lose all this flexibility to create custom faces.
Samsung watches for many may be a thing of the past if this isnt possible or if existing Watchmaker faces cant be converted.
Not possible to link the WFS (or the WFF) with anything… The only thing that can happen, “to link” with something external, is the user add a complication, but still, you have no access to the data… you can set the font, the color, the location, but no access to the data.
As far as I know, there is no function on WFS that returns the length of a string…
Hi it’s not the same thing you ask to do, but it’s very similar. and you can play with both the length of the text and the scrolling speed. Ch3st3rK.wfs.zip (340.3 KB)
ok thanks, I assume that with these changes from Google that all watches that have WearOS will eventually be affected and unable to use Watchmaker. So our hands forced into using WFS only? thanks
I don’t think so. If I understand it right, only those watches, which have wearOS5 from factory, enforce the use of WFF watch faces only. Watches that got updated to wearOS5 should be able to use older format of watch faces.
I don’t know of any tools for new watch face format other than WFS. Maybe Android Studio?
Newish devices are limited to WFF. WFS produces WFF, but WFF can also be created in other environments such as Visual Studio Code and Android Studio. Those aren’t WYSIWYG, but you can get near-real-time previews using an Android Virtual Device.
WFS handling of complications is easy to use but very restrictive. Using WFF directly, you can access complication value (etc). I’ve done that to recolour other elements based on the value of a complication.
WFF is XML. As such, it doesn’t support variables or procedural code (except in expressions).
WFS lags behind WFF in some regards. WFF has a text length function that can be used to resize text. Better still, WFF has an isAutoSize attribute that does so automatically. Those things will probably make their way into WFS eventually.