I think you are talking about the tap image and they always have been rectangle areas. Samsung has well documented tap areas. You can ask for that as a feature request, I don’t believe it is possible but you can request it as a feature request.
I hope, with the 8 complication limits there should be plenty of space for tap able areas and that makes it moot.
Ron
Samsung Developer Relations
Hmm not really, I am talking about circle complications and how they are a broken feature right now. It was implemented right in the latest beta 1.4.13. Samsung documentation says its content should be masked by the circle (evidence attached and here is the source) but right now the mask is not working. It is behaving as a box/rectangular complication.
The latest version is WFS 1.4.20 (no longer beta)
Are you saying it was correct in 1.4.13 and now broken. Or are you saying it was broken in 1.3.13… or did you mean
It was not implemented right in the latest beta 1.4.13.
I will handle this in 2 different ways if it is a bug or a feature request.
Ron
Samsung Developer Relations
Sorry. I meant it was working fine in 1.4.13 (Beta) but stopped working in 1.4.19 and it is still broken in 1.4.20 so it is NOT a feature request, it is a bug. Thanks.
Thanks for the clarification. I’ll ask if they did this on purpose.
Ron
Samsung Developer Relations
I was told it is fixed and they are waiting on an update (I believe a Wear API 33 update) It should be working on Wear 3 now. let me know if it isn’t sometimes the engineers say it is fixed but the fix isn’t released yet 
Ron
Samsung Developer Relations
I updated my projects with the new WFS 1.5.7 (Beta) and it is working correctly now! Thank you, so much!
I sincerely hope that the RANGED_VALUE will be added to the Small Box, for the afformented issues that I’ve mentioned previously.
Because like I’ve said, this can cause design constraints due to functional issues, as I’ve shown in the pictures above.
Thank you.
I do not think they have any plans on that. They expect you will just resize the Big Box to a smaller box.
I’m not sure what issues you are talking with a short text and ranged text?
Ron
Samsung Developer Relations
The issue is how the Circle Complications have to be resized to that everything inside the mask shows properly and do not go out of bounds. The problem is, by doing so, the complication area will also have to be larger, and they will take much more space than a box. I have shown a picture presenting the problem.
The problem is, there isn’t a combination of RANGED_VALUE and SHORT _TEXT is a line/Box form. You may want to click to a particular complication but instead, you’ll be clicking to the other one besides it.
The Circle Shape is great for making analog watchfaces but highly inefficient, when making a watchface that wants to show as much as data as possible.
@amoledwatchfaces
is there a difference between short text and long text for a complication?
Large Box has
Progress bar and text for range value type
Okay, I think I see where there’s a bit of disconnect.
SHORT_TEXT and LONG_TEXT are not the same type of complications
One does not substitute for another.
SHORT_TEXT is self-explanatory. You show a small amount of text to show data. Short and to the point. For example:
Samsung Weather shows Icon + Temperature (TEXT).
LONG_TEXT allows you to show a larger amount of info:
Samaung Weather: Icon + Temperature (Text) + Name of City (Title).
As for the differences, SHORT_TEXT type is the most commonly used type of complication. Plenty of apps use it. This is not the case for LONG_TEXT. Also, using a LONG_TEXT in a small area is usually not a good idea because more often than not, a lot of info will end with a “…” at the edge of the text. That’s unsightly to see.
In this case, you want to use a small area to show a particular info, a SHORT_TEXT is more favorable.
Also, another thing. Not every apps use the LONG_TEXT format.
Here are a few examples.
Sunset/Sunrise are SHORT_TEXT only.
Feels Like is SHORT_TEXT only as well.
For Third Parties: WhatsApp’s complication is only a SHORT_TEXT type as well.
So no, the LONG_BOX is not a replacement for the Circle Shape.
There needs to be a Circle equivalent in a line/box shape, because of how the masking and complication area works.
This is the issue that I am trying to get accross.
Can I just narrow this down to you wish to add SHORT_TEXT type to to LONG_BOX slot type? or am I still misunderstanding.
Ron
Samsung Developer Relations
Ron
That could work just as well!
I’m not sure if this is the same issue or not, as it seems multiple things were addressed in this thread, but the issue I am running into is that small image complication does not enforce the circle mask. For example, if I choose a Favorite Contact for the small image complication, the contact image is a square instead of a circle. On the other hand, if I use App Shortcut in the complication, the shortcut is a circle. I would love for the ability to force the resulting image to be a circle, as the mask suggests it should be.
What complication slot are u using, circle? If i not wrong the complication “icon/image” is auto provided by the complication u cant change it. Same as app shortcut…i also notice 2 different icon/image for complication and app shortcut… this is the app developer doing i guess
Yes, the circle complication restricted to the small image option.
I used google wallet same thing.
I may not be understanding the abilities of WFS and how it interacts with information provided by the app supplying the complication data, but it seems like the slot bound could/should act like a mask for the information provided to the complication. Because the shape of displayed information affects the aesthetic of the watch face. That’s one of the reasons we have different complication types, so we can display different information in different layouts, etc. I had hoped the slot bound would mask the information.
@ttnicky , sorry for the confusion, I tested on my GW 5 pro I don;t see your issue.
i used circle complication and the image I get for favourite contacts (contact’s imag is circle). the rectangle image I got was for small box complication.
anyway the slot bound crop text but for image it seems to be scale properly by the complication
what Watch and OS are you using? (is watch updated?)
WFs version?
sorry if you did tell me this details before but i forgot
