But Ron – and sorry to be a pest – but there is no way that I can see to do any of the above, through any mechanism outside of the inbuilt tags.
Let’s say I have a complication provider that supports ComplicationData.TYPE_RANGED_VALUE. It provides Value, MinValue, MaxValue, ShortText etc…
There is no way that I can see, that let’s me do anything with those fields.
I am probably mixing up my jargon, but the feature request is to allow a Watch Face Complication and/or a component to react and use those values — not just the built in tags.
As you say – Complications can use the Value, MinValue etc… but it can’t react to them and rotate a subcomponent, or change opacity or whatever based on those passed in values. It can only do it on the predefined tags. So, beyond Battery, Time, Steps and Heart Rate – there is no ability to do the above that I can see.
If we could have support for [value], [short_text], [minValue], [maxValue] then it would, I think, work.
Hard to explain this stuff sometimes. Hope that helps.