libretro / libretro/RetroArch

[Suggestion] Keyboard auto-detect

Open
#12,282 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

distro: lakka platform: rpi4
Dominant language
C
Stars
14.1k
Forks
2.2k
Avg merge
7h 35m
Merged PRs (30d)
51

Description

Raspberry Pi 4 B 4gb
Lakka OS Nightly RPI 4 arm Apr 15 2021

Hardware: USB Keyboard and USB Mouse
Cores: DosBox and DosBox-SVN

Im not sure if it is a bug, but when I started a first time setup and attempt at DOSBox the keyboard was not allowing me to input certain keys. IE P was pausing, I quickly had to delete all the keyboard hotkeys, then when Enter and some other keys such as the arrows and x was not inputting I went to controls to change them from gamepad to keyboard and mouse for the core.

It still did not allow me to use those keys until I disconnected the gamepad so RA will not get confused, then using the Keyboard I had to change it from gamepad to keyboard+ mouse and then delete the keys form the input list.

I went ahead and then tested it out on RetroArch (1.9.1) that was installed on my Linux Mint 20.1 Desktop PC. I never had DosBox on it so I downloaded the core and saw that it was doing the same thing there.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the behavior on RetroArch 1.9.1 with the DosBox or DosBox-SVN core, using a USB keyboard, USB mouse, and gamepad on the reported Linux systems. Compare keyboard input with and without gamepad bindings; done should mean keys such as P, Enter, arrows, and X work without deleting mappings or disconnecting the gamepad.

Written by the indexing model from the issue text.

Assessment

Tech stack
linux, raspberry-pi
Domain
frontend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.