XInput extension, xf86XInput, evdev and a spaceball

[Simon Thum]

Peter Hutterer wrote:
> the special case is two axes mapped to the same logical axis which has
> caveats for both approaches.
> if the labels change around with the mapping you don't know which axes are
> available anymore (axis N can be either physical pressure or proxmity).
> if the labels stay fixed, you don't necessarily know which axis an event was
> generated from.
This sounds as if it's worth considering a distinction between
'physical' (driver-specified) and logical (potentially user-specified,
thus more interesting to applications) axis labels. Net effect is that
some amount of configuration can be shared across apps, while retaining
the app-maps-by-itself case.

Cheers,

Simon