dosbox-libretro
dosbox-libretro copied to clipboard
libretro
Hotkeys interfere with keyboard input
If you are using a keyboard to run commands on the dos prompt the user will inadvertently toggle various retroarch options (such as pause with the p key).
What are the best workarounds?
What would the actual solutions be?
Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.
There is a pretty good workaround for this, which is to set input_enable_hotkey_btn in retroarch.cfg.
Maybe something along those lines could be a core option?
There's another thing you can use now called "game focus mode" or something like that. It works like mouse/kbd capture on e.g. Virtualbox. That is, it forwards all of the input events directly to the core instead of letting the frontend listen to them first.
I opened the retroarch.cfg file in a text editor, scrolled past the input_player1 section and typed in "nul" for each and every keyboard commands besides F1 (RetroArch menu) and volume up and down.
Now I can type in what I want without accidentally hitting a keyboard hotkey is dosbox libretro.
There are a lot of great solutions to this problem that can be used. I think this issue can be closed once the workarounds are documented.
Or should one of them be there by default for this core?
On Apr 7, 2017 5:27 PM, "Gagert" [email protected] wrote:
I opened the retroarch.cfg file in a text editor, scrolled past the input_player1 section and typed in "nul" for each and every keyboard commands besides F1 (RetroArch menu) and volume up and down.
Now I can type in what I want without accidentally hitting a keyboard hotkey is dosbox libretro.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/libretro/dosbox-libretro/issues/52#issuecomment-292656166, or mute the thread https://github.com/notifications/unsubscribe-auth/AAfjGYzywGe7M8QV-UTiXx1B2gvYQHvFks5rtqpJgaJpZM4MYz_o .
There are a lot of great solutions to this problem that can be used. I think this issue can be closed once the workarounds are documented. Or should one of them be there by default for this core?
Yes, I think so. I just had this issue. I found this thread, but it seems like a pain to go through and remove every single key. The other option should be a core option for sure.
game focus mode is the solution.
I do think it would be nice if there were a way for a core to communicate to the frontend that it's going to need the keyboard, but in the meantime having a hotkey to redirect all of the keyboard events directly to the core (i.e., keyboard capture, i.e., game focus mode) seems adequate.
Thanks, I found the focus mode. :)
Yeah, that's what I meant. It would be nice if during dosbox all keys were available except some key combo to bring up the menu. Alt-F1 or something unlikely to be used.
