Html-aam ATK mapping for METER element

[klown]

Role: ATK_ROLE_LEVEL_BAR
Interfaces: AtkValue, AtkRange

Reference:
"A bar that serves as a level indicator to, for instance, show the strength of a password or the state of a battery." (https://developer.gnome.org/atk/stable/AtkObject.html#ATK-ROLE-LEVEL-BAR:CAPS).

[jasonkiss]

Thanks, Joseph. Will update ATK Role and Interfaces.

Not sure if we need to be this specific, but AtkRange appears to be a component of the AtkValue Interface, as opposed to an Interface itself. That said, I'm not sure how best to refer to the type of structure it represents, or if it matters.

[jasonkiss]

Mapping updated, but leaving issue open pending resolution to question re AtkRange as interface.

[klown]

Thanks @jasonkiss

RIght, the range comes from the AtkValue. However, not all implementations of AtkValue support a range. In those cases, when AtkValue is queried for the range, NULL is returned. The case of a meter is one where the range is required. I thought that should be called out explicitly.

Reference: https://developer.gnome.org/atk/stable/AtkValue.html#atk-value-get-range

[jasonkiss]

Thanks @klown. I agree that mentioning AtkRange is a good idea. I guess my real question was more pedantic: AtkRange itself is not an Interface (it's not in the ATK list of Interfaces [https://developer.gnome.org/atk/stable/interfaces.html]), so listing it as one is not quite accurate. Is there a more accurate way to refer to it in the mapping than listing it as an Interface? Is it a property of AtkValue? Am I being overly pedantic?

[klown]

Thanks @jasonkiss. "You learn something everyday". My bad. I assumed that, like virtually everything else in ATK, that AtkRange was an interface as well. Your right, it isn't. It's just a struct. So, it would be misleading to document as one -- you are not being overly pedantic. Describing it as a property of the AtkValue is correct.

Thanks for your attention to detail.

[jasonkiss]

Ta. I've listed it as a Property. Assuming it is clear enough to implementers that AtkRange is implicitly a property of the AtkValue interface, I'm closing this issue as fixed.