Comment 2 for bug 669208

On Sun, Oct 31, 2010 at 19:07, tuos <email address hidden> wrote:
> Thank your for reporting this issue. You are missing the absolute
> parameter setting for ABS_Y axis. If you replace::
>
>  abs_parameters = {uinput.ABS_X:(0, 255, 0, 0)} #abs_min, abs_max,
> abs_fuzz, abs_flat
>
> with::
>
>  abs_parameters = {uinput.ABS_X:(0, 255, 0, 0),
>                                 uinput.ABS_Y:(0, 255, 0, 0)}
>
> then it works. Could you please test with that change and report back
> here the results.

Yes, it works that way :)

> However, I'm grateful for reporting this issue, because it shows me two things:
> 1. The whole module is badly documented (the documentation is missing totally).

Well, i think that adding a joystick example will improve things a lot.

> 2. Device-class should provide reasonable default values for abs_parameters.
Not only that, now if you doesn't specify abs_parameters it raises the
same error.

Thanks for the help!, python-uinput is super cool!