Are Multiple Mice Supported or Was That Feature Trashed?

Tango

@mitu said in Are Multiple Mice Supported or Was That Feature Trashed?:

@Tango said in Are Multiple Mice Supported or Was That Feature Trashed?:

I would think the Mouse Index would be the same number as the mouse device node or the event node.

Not really, the number assigned to the device is not necessarily the index of said device in the list of same-kind devices. For the /dev/mouseX, it might look like it is, but the /dev/input/eventZ are for all event generating devices (keyboards/gamepads/leds/mice/etc.).

Let's say you plug in 3 mice, they get /dev/input/event1, /dev/input/event2 and /dev/input/event4. The indices would still be 0, 1, 2 (or 1, 2, 3 of numbering is from 1). Now, you remove the 2nd mouse, so /dev/input/event2 disappears, but the device in /dev/input for the remaining mice are the same, while the index for the 3rd mouse would shift downwards.

Okay, doing my rephrasing thing to see if I get it:

Since my system used /dev/input/event3 and /dev/input/event6, I probably had some other device using something between 3 and 6, so /dev/input/event3 was Index=0 and /dev/input/event6 was Index=2, with some unknown dongle being in between at /dev/input/event[4 or 5] and that got Index=1.

Is that saying the same thing?

mitu

@Tango said in Are Multiple Mice Supported or Was That Feature Trashed?:

Is that saying the same thing?

Yes. I'm impressed you managed to keep it under 1 page this time :).

Tango

@mitu said in Are Multiple Mice Supported or Was That Feature Trashed?:

@Tango said in Are Multiple Mice Supported or Was That Feature Trashed?:

Is that saying the same thing?

Yes. I'm impressed you managed to keep it under 1 page this time :).

You have no idea how much editing it takes to sort through what's in my head and make anything short!

But there are also times I would rather have too much detail than leave out something important.

Tango

@mitu

@mitu said in Are Multiple Mice Supported or Was That Feature Trashed?:

@Tango said in Are Multiple Mice Supported or Was That Feature Trashed?:

Is that saying the same thing?

Yes. I'm impressed you managed to keep it under 1 page this time :).

If this is true, it seems to me you can't be sure just what the index for a mouse device will be and, if there is more than one, trial and error will often be necessary.

mitu

If you only have 2 mice, they should always have the same index.

Tango

@mitu said in Are Multiple Mice Supported or Was That Feature Trashed?:

If you only have 2 mice, they should always have the same index.

True, but when you're first setting it up, you can't be sure just where they are.

I'm still puzzled, since the trackball is 0 and the spinner is 2 and, as far as I know, there are no other mouse type devices connected. My best guess is that one of the MiniPacs must have an undocumented mouse device in it that uses 1.

mitu

You can check by looking at the RetroArch's debug log and by running cat /proc/bus/input/devices.
Remembering your first RetroArch debug log, my guess is that RetroArch counts twice a mouse device as both /dev/input/mouseX and /dev/input/eventY. You can check this theory by adding a mouse (so you have 3 devices) and using indexes 0, 2 and 4 to see if each device is detected and working.

Tango

@mitu said in Are Multiple Mice Supported or Was That Feature Trashed?:

You can check by looking at the RetroArch's debug log and by running cat /proc/bus/input/devices.

Is proc/bus/input/devices a totally separate log than in /dev/shm?

Remembering your first RetroArch debug log, my guess is that RetroArch counts twice a mouse device as both /dev/input/mouseX and /dev/input/eventY. You can check this theory by adding a mouse (so you have 3 devices) and using indexes 0, 2 and 4 to see if each device is detected and working.

I get that - and on the first time! Yes, that's something I can check to see what's going on.

Thanks!

(At this point, I'm just thrilled I got it working and can move on to the other UI issues, like changing around a few key bindings/actions to make it more user friendly with the buttons and labels on my control console.)

mitu

@Tango said in Are Multiple Mice Supported or Was That Feature Trashed?:

Is proc/bus/input/devices a totally separate log than in /dev/shm?

Not really a log, but a listing of what input devices are detected by Linux and how are they handled (i.e. which /dev/input/eventX has assigned, what type of device is it, what driver is handling it, vendor/model info).

Tango

@mitu said in Are Multiple Mice Supported or Was That Feature Trashed?:

You can check by looking at the RetroArch's debug log and by running cat /proc/bus/input/devices.
Remembering your first RetroArch debug log, my guess is that RetroArch counts twice a mouse device as both /dev/input/mouseX and /dev/input/eventY. You can check this theory by adding a mouse (so you have 3 devices) and using indexes 0, 2 and 4 to see if each device is detected and working.

Okay. I can see that now, with access to the computer again. (Remember, it's in a different place than my desktop, that I use for posting.) Thanks!

Now I have the primary Mini PAC set in Keyboard Mode and I see that it recognizes the Mini PACs as devices, but also recognizes the devices on them separately. It looks like keyboard in the Mini PAC gets an event node. Interestingly, the Ultimarc SpinTrak (the spinner) gets Event 5, not 6. When I test with cat /dev/input/event6 I get input from the spinner and I don't with event5.

But this shows me that some of the devices are broken down into multiple devices and explains why something else is "in between" the trackball and the spinner.

As a side note, even though this is a built in function for RetroArch, I've now done what the manufacturer claims can't be done. Xtensions claims that, in D Input Mode, you can only have one mouse device, so you can have the trackball (somehow that always ends up as the one to take priority) but not the spinner in that mode. I'll be writing them about that!

When I have all my questions worked out, I'm going to either write up a few blog pages or make a few videos for others with the same issues. I'm hoping that they will use the so their other customers can get this working, too.