Autofire and autohold behavioral weirdness

The autofire and autohold modifier behavior has been odd from gens 10
onward, as astrange side effect of the hotkey customizability changes.

Basically, it used to be that, to enable an autohold or autofire, you had
to press the modifier, and then the key you wished to toggle. This was true
for disabling the hold or rapidfire as well.
Now, however, you can enable autohold or autofire by pressing the modifier
while the key is held, but disabling still requires you to be holding the
modifier as the first key in the combination (or hit the clear holds hotkey).

I don't know why I haven't made an issue report of this previously, since
it has been constantly annoying me as I accidentally activate holds and
such without noticing, and then have to load state and deliberately turn
them off.

Original issue reported on code.google.com by Upth...@gmail.com on 9 Mar 2009 at 10:05

timblepaw / gens-rerecording

Autofire and autohold behavioral weirdness #58