Let me try to explain EXACTLY what my 'problem' is (no, not that problem, nor that problem, nor that one either

), with regard to peripheral devices.
I shall use as an example my Genesis Thor 100 rgb (which is, as someone remarked, a bit outdated: so, hell, am I, and I picked it up very cheaply indeed because I did NOT want the latest 'thang' to play games with, but a 'thing on the left' to stop wrist cramp) as it is the peripheral that happens to be connected to the computer I am sitting in front of at the moment.
So:
1. If I hit the 'Q' button on the gamepad I get a 'q' sent to my OXT stack.
2. If I hit the 'Q' button on my keyboard I get a 'q' sent to my OXT stack.
No prizes for that one!
HOWEVER, what I wonder about is whether there could be a way inwith the OXT IDE to work out whether that 'q' signal was originating in the gamepad or the keyboard.
IF there were a way to detect where the 'q' originated one could set up a series of "macro" commands/functions in a stack so that Chummy playing the game one has authored in one's stack could, for the sake of argument, control the movement of the "zombies" with the gamepad, while using the matching keys on the keyboard for something quite different.
Many gamepads come with software to set up macros (my Belkin Nostromo n30 and n50 cam with this software for Macintosh 32-bit), but they tend to be confined to one or two operating systems (my Genesis Thor 100 has a set up thing for Windows 8 only): and an end-user will not necessarily set their device's macros up the way the programmer of the OXT game wants.