The data would need to be transferred using a complication rather than a tag (as I think you know). A RANGED_VALUE complication can pass a number to a complication slot. It’s possible to configure WFF (and I think WFF) to limit a complication slot to one specific complication source. The killer might be that third-party complication can only update once every five minutes (or when touched), which isn’t useful for real-time data.
1 Like
Understood. I agree on the utility point, a wind direction that updated every five minutes is no big deal but a compass viewer would have to update frequently enough to appear live for any utility. Oh well, I revert to my yawn about how much WFS lacks compared to, say, Watchmaker Pro (which can’t…yet…create WFF faces the last time I looked).
The limitation isn’t WFS. The limitation is WFF. WFF is the only format of watchfaces that can run on new devices. Any new version of Watchmaker or anything else must target WFF (just like WFS does), and won’t be able to get around WFF’s limitations.
Pardon me, I did understand the problem is WFF, and thank you for the posts. The limitation does, however, transfer as a limit to WFS capabilities for end-users who are just making watch faces they like. I understand this isn’t the place to ask for corrections to such things but I rather hoped Samsung has a louder voice when talking to the, let’s call it, Android (or Wear OS) community.
I understand. I’m sure you’re right that Samsung has more influence than any of us. Even if there was a way of applying to get appropriate complications able to update more frequently, that would help considerably. WFF does actually allow that, but only system integrators (ie, manufacturers) are granted access to it.
1 Like
Lol, I remember making working compass bezels in Watchmaker like 5 years ago…a wonderful time.
2 Likes