Comment # 14
on bug 8579
from Evan Huus
(In reply to comment #13)
> I think they should be simply registered as FT_FLOAT. I will take a look. I
> was a little bit confused because I think I saw a warning once when I was
> registering FT_FLOAT shorter than two bytes. But it was probably when I was
> not yet using custom way to display floats. Obviously I didn't correct all
> the UINT8s to FLOATs.
>
> Using own way to present floats is the only way in our case. In the protocol
> there can be a float long only 7 bits or even shorter. In fact float is
> never stored as floats usually are with sign, exponent and fraction. They
> are always integers and then the scaling factor is defined. For instance,
> flight level is stored as integer with LSB (least significant bit) 1/4FL.
> Value 50 is actually 12.5. Showing 50 would make no sense. So I decided to
> show them as floats because decimals are important.
That makes sense, and seems to be the correct way of doing things for this
protocol.
You are receiving this mail because:
- You are watching all bug changes.
