On 29 May 2014 18:54, Jason Gerecke <[email protected]> wrote: > If that's the case though, I have to ask -- *why* on Earth is > 'li_fixed_t' even being considered as libinput's output type? I know > I'm missing something because the thought seems like such a blindingly > terrible choice. Its not an intrinsic type, is ill-suited to the task > of representing normalized data, and can't be directly used without > very real overflow concerns. By contrast 'float' is a standard type > which takes up the same space, offers sufficient precision of > normalized data, and can be freely operated on without concern. Is > there some crazy reason that floats aren't viable as the output type? > Are we communicating over the Wayland protocol despite being a > library? Targeting hardware with no FPU? libinput seems like it could > be useful to more than just Wayland compositors, so I _really_ hope > the reason isn't to maximize the degree of integration between the > two.
Both Wayland and X11 use fixed-point types over the wire. Obviously none of this is driven by no-FPU, because even on ARM that isn't a thing.
_______________________________________________ wayland-devel mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/wayland-devel
