IssueTracker

Hello,

I wasted hours trying to change text size. It doesn't work (as documented), and I'm very unhappy as a result.

Here's an attached reproducing apk (you can read the XML by drag'N'dropping it into AS and navigate to res/raw/watchface.xml).

I set 3 overlapping fonts with different sizes, but you'll see only one because the size never changes in the renderer. After hours or zero productivity, I found that it works if I don't use decimal notation. WHAT???

This behavior is horrendous since the docs say "float" when it comes to Font and BitmapFont.

Misleading in a very bad way 🙁🙁🙁☹️☹️☹️ There were many, many hurdles in figuring out the WFF format, and it keeps giving, I'm so tired of that, and it's so far from what I'm used to from Google 😔

1. The debug experience is super bad, please, show something on the device screen when there's an error, e.g. a red outline for a few seconds when the watch face is first drawn after update or reset, so that we know there was an issue.
2. Please, make sure the renderer, WHICH WE HAVE NO WAY TO FIX, is bug-free
3. Please, make sure the documentation is correct, and not lying or misleading. The current situation is unacceptable. I found more than 30 problems and inconsistencies in it, and probably forgot some, and that doesn't count the false "float" problem I'm just reporting for Font and BitmapFont.
4. Please, release some better examples, the "SimpleAnalog" and "SimpleDigital" ones on GitHub are really uninspiring, and I'm sure you made better examples internally which would be helpful to other developers.
5. Please, provide XSD/XML schemas, that don't lie, so we get a better understanding of the schema logic. I can see a lot of repetition in the attributes, a schema would help trace it, and would make diffing easier when you'll update the specification for future Wear OS versions.
6. Please, consider making a compat renderer from watches that are not running Wear OS 4
7. Please, consider making a desktop preview renderer (Compose Desktop based maybe?), that shows the issues and error in real-time.

I hope you agree that the debugging situation is really bad, a far cry from what we usually have on Android, and that the documentation is not very developer friendly.

Please, talk about those problems internally, don't let it go to waste.

Thank you, and have a great day!

Louis CAD