-
Notifications
You must be signed in to change notification settings - Fork 24
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Physical arrow keys not working as MO/TO arrows #11
Comments
Hi! |
Yes it occurs in both modes and can be seen in the Basic environment, where the arrow keys generate digits. I don't think I left a wrong setting in Retroarch, as the keyboard arrow keys are working correctly in the Microsoft Basic environment of the BlueMSX core (they control the cursor correctly). By the way, in TO8 mode, after entering the first Basic option (1), I cannot type a double quote character (required for RUN"). Regarding the joystick emulation, I did not manage to use a joystick with L'Aigle d'Or as a backup solution. |
In MO5 mode and in the latest recalbox beta, there is no problem : the arrow keys move the cursor. |
Hi! |
Hi, thanks for all the quick answers. |
You're welcome. |
Following discussion with RetroArch developers about keyboard layouts and recent changes done on RetroArch 1.7.6 on this topic, I made major changes on the keyboard emulation that should fix all the problems (I still have to test these changes on Windows though). |
Hello,
Under Retroarch 1.7.5 on Windows 10 x64, with Theodore core v. fee726b, I cannot have the physical arrow keys from my keyboard working as MO/TO arrow keys.
Under MO/TO Basic, these keys input the characters "2", "4", "6", "8" instead of moving the cursor (as if they were the arrow keys from the numerical keypad).
I made sure to use "Enable hotkeys" hotkey in Retroarch, disabled the Retropad, and also used the "Game focus toggle" hotkey to disable all other hotkeys, but the behavior remains the same.
This is a blocking issue for games like "L'Aigle d'Or", which can only be played with the keyboard.
This issue is not present on DCMO5 v6.8 (used via Dosbox).
The text was updated successfully, but these errors were encountered: