Possible "OK" bug?

[bobross]

I was having the hardest time trying to configure some new buttons using mame32s through GameEx. When I would press enter and tap a new key I would always also get an O or a K in the field. Is gameEx constantly sending an OK key press to bypass the disclaimers? This is not a huge problem as I can configure games straight through mame.

Where I was thinking this could be a problem is my HotRod SE encoder does not like many more key presses then I already assault it with. Can this be the cause to the occasional joystick gets "stuck" in one direction for a couple seconds at a time problem?

[Tom Speirs]

I was having the hardest time trying to configure some new buttons using mame32s through GameEx.  When I would press enter and tap a new key I would always also get an O or a K in the field.  Is gameEx constantly sending an OK key press to bypass the disclaimers?  This is not a huge problem as I can configure games straight through mame.

Where I was thinking this could be a problem is my HotRod SE encoder does not like many more key presses then I already assault it with.  Can this be the cause to the occasional joystick gets "stuck" in one direction for a couple seconds at a time problem?

It does stop sending OK after 5-20 seconds, maybe I need to lower how long.

[headkaze]

Tom, have you tried using the WaitForInputIdle() API function just after launching Mame, then sending the "OK" then instead of sending it over and over?

[Tom Speirs]

Tom, have you tried using the WaitForInputIdle() API function just after launching Mame, then sending the "OK" then instead of sending it over and over?

Thanks for the tip. I will try it, see if it works