In #8 I proposed a name of first PropertyType, then TrackedDevicePropertyValue, for the trait that is currently called TrackedDeviceProperty. We punted the naming discussion so that we could just get the PR merged.
Here are my arguments why we should change the name:
The value of the property is not the property itself. A u64 is not a property in and of itself, but a struct can have a u64 property named 'foo'.
The type of the enum being passed to openvr is ETrackedDeviceProperty, and they return a value of one of the types that implement this trait.
I think of this as a key-value map, i.e. HashMap<(Prop, TrackedDeviceIndex), Any>
I'd like to use the name TrackedDeviceProperty for the trait that refers to 'types that act like ETrackedDeviceProperty' in #19
For now I'm using the name TrackedDevicePropertyName for this, but this feels really clumsy, and doesn't match openvr's naming.
In #8 I proposed a name of first PropertyType, then TrackedDevicePropertyValue, for the trait that is currently called TrackedDeviceProperty. We punted the naming discussion so that we could just get the PR merged.
Here are my arguments why we should change the name:
HashMap<(Prop, TrackedDeviceIndex), Any>TrackedDevicePropertyfor the trait that refers to 'types that act likeETrackedDeviceProperty' in #19TrackedDevicePropertyNamefor this, but this feels really clumsy, and doesn't match openvr's naming.