for the linux plugin I can say that it works although there are 4 abs axes which do not do anything - thats why in my plugin i just ignored them. please have a look at the minimum and maximum data the kernel provides. the problem with these axes is that they marked as being pressed constantly (-1) which is very bad for input autodetection.
Is this a new problem, or did it do this with what was in CVS? Can you send me the dump from a texttest and readtest?
another bad thing is that my pc speaker is still a non-usable but visible input device.
Ok, I now throw away anything that has no sub controllers and/or no components.
another small problem: Controller.getAxes() still exists but returns the Component array. apidoc is outdated too.
renamed method and updated the docs (I think I got them all)