You guys will have to be a little more specific by what you mean. At the OS level it is one device for me so that's how I represent it. If there is something specific that you're talking about lemme know.

Hi I thought I explained this, guess my explination was poor . The Mouse under windows and linux plugins is represented as one device, with two subdevices, one subdevice for the MouseBall and one for the MouseButtons, take a look at the classes net.java.games.input.Mouse and net.java.games.input.DirectInputMouseDirectInputMouse constructor constructs itself with a BallImpl and an ButtonsImpl, which extend Ball and Buttons from Mouse, these are the devices that actually have axes in them, DirectInputMouse doesn't, and for consistancy I did the Linux one the same way. That is what we mean by two devices, rather than one.

Okay, and how is this different from what the OSX version does. What I need someone to say is 'here is what you did in the OSX version - could you do it like xxxx.' Without a clean spec, I just implemented it the easiest way for OSX.

That's how I kept getting confused because I couldn't understand what I had done differently as I'd simply followed the Windows code making modifications to the Impl classes to match what I needed for OSX. There is an OSX mirror for every DirectInput class

java-gaming.org is not responsible for the content posted by its members, including references to external websites,
and other references that may or may not have a relation with our primarily
gaming and game production oriented community.
inquiries and complaints can be sent via email to the info‑account of the
company managing the website of java‑gaming.org