My first question is that ints are allowed in the api, so why is it not
using them instead of fixed. I think it is a lot clearer to say the
maximum value is 0x7FFFFFFF than 16777215.99609375. The bit pattern sent
is identical so it is simply a documentation question.
I'm now thinking that normalized is not necessary and does not help.
This is because the library must now send a "resolution" value so the
client can know how far apart the stops are. This is 4 numbers: the
value, the range, and the resolution.
It would work better to send an integer giving the position in stops
minus the position of "zero" in stops, and then two more integers giving
the min/max values in stops. This is three numbers: the value and the range.
In both cases the client may also want to know the physical units the
device positions are in. I guess this would be an enumeration describing
the "unit" (including a power or log modification of an si unit) and a
scale factor that says how big the range is in units. However this is
done it adds the same amount of data to the api.
_______________________________________________
wayland-devel mailing list
[email protected]
http://lists.freedesktop.org/mailman/listinfo/wayland-devel
