If you think about it as a communication to the API, I think it makes sense.
The API reads the property before reading the data, if the data is "unscaled" then it should apply the scaling information before providing the data to the requester.
If the property says "scaled" then the data stored in the TDMS is already scaled, so it should NOT apply scaling to the data (otherwise it would be double-scaled).
I think this is an "internal property" and we're just messing with things 😉
That doesn't really explain the odd "read property" behavior though...
That oddity is why I think I ended up using the "number of scaled" = 0 instead, because it was traceable.... I could read that value, make a decision based on it, change it for the read operation, and then revert the value to the original leaving the data "intact"
You can't really do that with the other property because of the weird property read behavior.
