Axis.Identifier

[endolf]

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)

Endolf

[swpalmer]

Hi
 Right, for now the name stays as Axis, ...

Apparently not?

Thumbs down to the rename.

[endolf]

1   2   3   4   5   6

public class Axis {     public class Identifier {         public class Key extends Identifier {         }     } }

Will result in compile errors

Endolf

Games published by our own members! Check 'em out!

[swpalmer]

Are you sure you want all those inner classes?  Seems a bit twisted. Maybe you want to stick 'static' in there somewhere?

e.g.

1   2   3   4   5   6

class Axis {   static class Identifier {   }   class Key extends Identifier {   } }

[endolf]

I did ponder pulling Identifier out into it's own class, but the identifier is unique to a component/axis/whatever we call it. I also pondered creating a package for the controls and pulling out keys from the keyboard, and axis class, a component interface and a button class, then moving the Identifier object in there, or even having identifier as a package inside the component package and placing Identifier, KeyIdentifier, ButtonIdentifier and AxisIdentifier in there. If thats what people would prefer, then we could go that way too.

Endolf

[swpalmer]

I don't understand why you would do all that.  But maybe I'm simply not getting it.

It seems to me that Axis.Identifier fits well.

That is Identifier as a nested class of Axis, not an inner class.

That is the CLASS not the OBJECT.  Each Axis can have a member object of type Axis.Identifier.

[swpalmer]

Someone needs to invent a "programmers forum" where it is easy to create UML diagrams in the message threads

[endolf]

Hi
 Ok, Identifier as a nested class rather than an inner class, thats not a matter for debate really, it makes sense, i've done the change (not that it's hard), i'll commit it later when I'm not on works vpn and can actually use things other than port 80. Grr atta nasty vpn software that won't let me access *anything* except the vpn'd network, not even me own lan.

Endolf