When emulation is stopped, it is impossible to test keys since keypresses are tested by code and need the button to be pressed for a certain amount of time before being released in order for the key to register. The time is in the millisecond range, and is affected by how fast the clock rate is.
My initial idea was to have a "hold" mode that keeps the buttons "pressed" for several cycles, but a far easier approach is to just toggle the keys.
This could be a manual setting, or an automatic one that is enabled when the emulator is stopped.
The last release added indicators that the button was being pressed, so this works hand in hand with that.
With toggle keys, pressing a button or key on the keyboard will hold the button down, letting the emulator code register the press while, for example stepping through the code.
Clicking or pressing the corresponding keyboard key again will release the key.
When emulation is stopped, it is impossible to test keys since keypresses are tested by code and need the button to be pressed for a certain amount of time before being released in order for the key to register. The time is in the millisecond range, and is affected by how fast the clock rate is.
My initial idea was to have a "hold" mode that keeps the buttons "pressed" for several cycles, but a far easier approach is to just toggle the keys.
This could be a manual setting, or an automatic one that is enabled when the emulator is stopped.
The last release added indicators that the button was being pressed, so this works hand in hand with that.
With toggle keys, pressing a button or key on the keyboard will hold the button down, letting the emulator code register the press while, for example stepping through the code.
Clicking or pressing the corresponding keyboard key again will release the key.