Can you forgive me little rant earlier? Sorry. I've had a good play with it now and I think it's working. And I understand what you mean by pressing the hotkey and F1. Is there a way to have it by pressing F1 alone?
I've Reset Retroarch config and plugged in a Wired Mouse and keyboard and OP Wolf is working now.
I've also changed my RetoArch to Ozone just like my PC. It's much less confusing now. It's going to take some time to get used to this :)
Ah, so you're thinking of capturing the mouse up/down movements and sending them to ES as joystick movements. ES wouldn't know the difference. Not bad. My set-up isn't wired to pull this off, but it's definitely an idea.
I currently use my trackball as a mouse in PIXEL. It'd be nice to scroll through ES with my trackball, but alas support is not included.
May I suggest you unplug any wireless (game) controllers particularly using bluetooth. I had the same issue but the problem was resolved when I'd disconnect my XBOX One controller via bluetooth and used a wired keyboard,wired mouse and a wired controller/
@Bluebotlabs I know what your original post was asking. If you want mouse support right NOW, you can use the pegasus frontend as an alternative. It uses emulationstation's scraped art/gamelist info except for logos/marquees.
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.