for a few versions, multiple mouse was hardcoded on
Can you give me some more info on this please? Like when it was hardcoded, then when it became selectable. Or point me in the right direction.
When mame changed from DirectInput to RawInput for the mouse, no previsions were made for lots-o-mice-to-act-as-one-mouse to continue, as the change was done to add support for multiple mice to control different players to winXP. (
0.104u5) IIRC, the thought was you could still remap to "use any mouse", and adding commandline options were discouraged.
The -multimouse and -multikeyboard options were added starting with
0.117u1. I think the thought was too many people complained about the "mouse not working" with the above setting, even though it was working just not acting like the windows pointer cursor does. (Now the problem is that people enable this option when they don't want to.)
So... from 0.117u1 and and on, we've had -multimouse option defaulting to off. Disabled acts like the pointer cursor does in windows desk top with multiple mice plugged into the computer: all mice control the same pointer/player, and the app cannot tell which physical the info is coming from. Enabled, mame can see each mouse separately, so you can do things like play 2 player marble madness.
Between 0.104u5 & 0.117 (inclusive), mame acted
as if the option was "hardcoded enabled", even though there never was (yet) an option to hardcode in the first place. Mouse 1 controlled player 1, mouse 2 did player 2, etc by default. To map so any mouse could control P1, you could remap player 1 TB to mouse 1 or mouse 2 or mouse 3 etc, but people didn't like this or had problems remapping.
Ending with 0.104u4, mame acted
as if the option was "hardcoded disabled", even though there never was (yet) an option to hardcode in the first place.
(Win9x was a different story, as it acted as if -multimouse was both enabled and disabled for a long time before 0.104u5, but I won't waste space unless you want me to go into it.)