I designed this simple watch face containing text elements for Time, Date, and percent of battery available. Then at the top of the display I added one complication. This is what it looks like in studio:
Once the watch face is loaded onto the watch, if I select “Number of Steps” for the complication, the watch looks like this:
This is exactly what I expected
If instead I select “Sleep time” for the complication, the watch looks like this:
Again, all is working as I wanted. However, then I select Heart rate for the complication and now the watch looks like this:
oops … this certainly seems like a bug. Unlike the other complications, the heart rate complication seems to be ignoring the image and font sizes that I chose in my watch design. It’s true my eyes are not what they were when I was younger, but this is truly microscopic. I can read the other elements without even putting on my glasses, but I can barely read the heart rate even with my glasses on. I hope I’m missing something obvious, because if this is what Samsung expects me to use, it would be ridiculous.
Thanks in advance for any suggestions you may be able to offer.
That complication is probably not providing a ‘Title’ field, so a different layout is used. You can select each such layout in WFS and customise them separately to each other.
Hi Russell. Your answer is even more mysterious than the one from Gondwana. “The error is due to the maker of the App” … what App? The only app we are talking about is Watch Face Studio. So who should I contact? … or “use a different one” you say. You mean a different watch face designer??? Are there other watch face designers for the Galaxy 7 watch?
It would be one thing if I was trying to use some obscure feature. But heart rate … that’s almost the reason for smart watches to exist. So it is hard for me to imagine that the heart rate display doesn’t work.
There are several different types of complication (RANGED_VALUE, SHORT_TEXT, etc). Within each type, many of the possible fields are optional, and a different layout is used depending on which fields are provided by the complication. It seems like you’ve fully customised one particular layout for one particular type, but have not customised the layout for the type that is provided by the heart-rate complication. Have a look down the right side of the WFS window and you can see all of the layouts you need to consider.
I semi-agree with Russell. The heart rate complication is a totally separate app to WFS, and to the watchface app that displays the watchface. However, it isn’t compulsory for complication-service apps to populate all possible data fields, so what you’re seeing isn’t a bug.
I didn’t realize the heart rate complication itself was an app. I didn’t load it separately … it was just there. Are there other heart rate complications? If so, where would I find them and how do I load them. Again I find my confusion surprising given the importance of heart rate in the smart watch world. Whether you call this a bug or not is not important to me … all I want to know is how to fix it.
@pmennen . Most profound apologies . I never use the Canned Complications . I actually use Complications on my Faces Hidden . I have never had any luck getting them to display properly . There are Tags for Steps Heart rate and many others I use them and have them displaying how I wish. I am sorry that the Heart rate Icon is not showing the right place . Of course there are no third party Apps for Heart rate . So sorry .
Heart rate uses Icon and Text, while Sleep and Steps use Icon, Text, and Title. Remove any complication display style you don’t need by clicking the x.
Thanks creationcue for your reply which was spot on. Before reading your reply I wasn’t even aware that there were different layouts for the complication. Once I configured the proper layout, the heart rate complication worked perfectly.
All the other replies before yours were well intentioned but useless. In there defense though, this is not an easy program to learn by discovery. I had the complication expanded to show the individual components that makes up the complication and in that view the radio buttons showing the various layouts do not appear, so I didn’t even know they existed. This leads me to ask how you figured this out. Was this by word of mouth from another useful reply on the forum, or did you learn by experimentation, … or was it something you read or watched (a tutorial, for example)? If it was the latter, please share the documentation or tutorial that allowed you to gain such wisdom! ~Paul
