> I would be rather surprised if being able to use the shift key to unpause in any
> remotely recent version wasn't just your memory playing tricks, because the relevant
> UI code hasn't changed since 0.121 aside from being translated from C to C++. From
> what I can tell, the shift modifier has been hardcoded in every release of MAME since
> single-stepping was introduced back in 0.36b4.
>
> I'd still call it a bug, since single-stepping appears to be the only UI function
> outside of menus, message boxes and special viewers that can't be remapped. Indeed,
> the GIT history shows that single-step was briefly made mappable during a sweeping
> rewrite of the UI menu code. I don't think this had anything to do with why the
> rewrite was reverted, though it clearly must have caused too many other problems to
> be accepted into 0.165.
Thanks for the response. It's definitely possible it's my memory playing tricks on me. I can't pinpoint when it started. I made some changes to my cabinet and it was out of commission for a bit so it could be longer than I thought.
I will log it as a bug on mametesters.org.
|
Index 
Flat 
Re: MAME bug - Can't unpause when SHIFT key is mapped to Pause function
Reply
