We’re thrilled to announce the release of version 8.5.0 on watchfacebuilder.com! 🚀 Here’s what’s new and improved:
- Introducing WFB API Key: We’re rolling out something special for our premium account users – the WFB API key! With this key, you’ll gain access to a premium services (more detail to come).
- Garmin SDK Data Fields: Added the missing Garmin SDK data fields recently released.
- Complication Value Retrieval: Now, you can fetch values directly from complications, ensuring your data is updated more frequently than retrieving it from sensor history table on your device.
- Bug Fixes: eg. resizing un-resizable objects and more.
- App Authentication: For our premium account users, you can add “app auth” data field on your design. Anyone can try your watch faces, and after the trial period, a message will show on the watch. Then users can contact you, and you can review their request on the back end of WFB site to approve or deny their access.
Hello, is there more detailed information for App Authentication, how do I integrate it and how do I use it? thank you!
I’m not sure if this is a new bug, but the “visibility” field sometimes disappears from objects after I’ve been customizing them. The custom formula is retained, but the field becomes invisible in the editor. If I “build” the design, it seems to work as expected, and it usually appears again the next time the editor is started.
Generally, I think these visibility tabs aren’t ideal. On my watch, hi/low, sleep/nonsleep, and dnd/nondnd seem like independent variables, so the modes are really like a 3-dimensional boolean space with 8 combos. I don’t know if some other watches might have other useful “dimensions” like these.
Ideally, I think the editor should allow set a compound boolean visibility formula. Some objects might only care about one dimension, while others might be for very specific combinations like only in high power + non-sleep + non-dnd. Then you want a preview tab that has checkboxes so you can toggle the individual variables and see the effective layout. I guess you’d either need a parser to interpret a subset of Monkey C boolean expressions, or maybe some kind of visual/structural rule editor that can be interpreted in the editor and generate the right Monkey C logic too…