Make input configuration more device-aware
Los mantenedores suelen responder en 1 día
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 5/5
- Tiempo estimado
- Más de una semana
- Aptitud para principiantes
- 25/100
Línea de trabajo
Start by tracing how the existing key configuration assigns devices and handles gamepads, keyboards, and local multiplayer. The issue proposes device-specific configurations, keyboard exemptions, and restrictions for custom multi-device setups, but names no files, tests, or entry points. Done means those rules are implemented while preserving the stated multi-device use cases.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
At the moment, if you connect two controllers, you have to configure both controllers individually in the key config to effectively gain 2 usable key configurations even if the controllers are the same (have the same GUID, should work with the same configuration but don't).
Applying input configurations by device instead of binding one or multiple devices to a single input configuration has various advantages:
- For anything detected as a gamepad we can just apply the gamepad configuration straight up.
- For gamepads, you no longer have the issue of only having stick OR dpad available.
- configuration setups that don't make sense are no longer possible, e.g. binding from several devices or having the same input bound to multiple input configurations in local multiplayer
- this includes making it more difficult to brick your input config to the degree that you have to delete the configuration file to start over.
- Once per-keyboard inputs are available, people are almost immediately able to use the same keys on different keyboards
Keyboard inputs should initially be exempt from this to allow people in local vs to work together to set up a configuration with no friction until the aforementioned per-keyboard inputs become available.
Obvious disadvantage is that you couldn't use legitimate multi-device configurations, e.g. foot pedal + joystick or other complementary input devices.
But all things considered these could still be made available with the current mechanics under the following restrictions:
- a device used in one custom configuration cannot be used in other special configurations
- a device used in a custom configuration cannot be used as its own main device anymore
- Lenguaje dominante
- Lua
- Estrellas
- 30
- Forks
- 20
- Merge medio
- 3 d 15 h
- PR fusionados (30 d)
- 17
Preparar el entorno
- Sin Dockerfile ni archivo de Docker Compose
- Tiene una plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de panel-attack/panel-game
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 65/100
panel-attack/panel-game#822 ·
Los mantenedores suelen responder en 1 día
-
Training lists duplicate classic puzzles because the training filter's set names don't matchAbierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
panel-attack/panel-game#779 ·
Los mantenedores suelen responder en 1 día
-
bug Client-side priority: 0 - high
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
panel-attack/panel-game#776 ·
Los mantenedores suelen responder en 1 día
-
enhancement priority: 1 - middle
Dificultad 4/5 3-5 días Aptitud para principiantes 48/100
panel-attack/panel-game#821 ·
Los mantenedores suelen responder en 1 día
-
Animation scenes draw every part separately, costing hundreds of draw calls a framePosiblemente ocupada @JamesVanBoxtel la tomó hace 4 días. AbiertoClient-side enhancement graphics
panel-attack/panel-game#814 · 1 asignado ·
Los mantenedores suelen responder en 1 día
Todos los issues de panel-attack/panel-game
Issues similares
-
slice weekend
Dificultad 2/5 1-3 horas Aptitud para principiantes 71/100
Life-Framework/Life-Framework#3212 ·
Los mantenedores suelen responder en 1 día
-
bug discord guide:01b-riverglades locale:enUS triage v4.1.1
Dificultad 2/5 1-3 horas Aptitud para principiantes 67/100
Los mantenedores suelen responder en 1 día
-
Dificultad 1/5 1-3 horas Aptitud para principiantes 84/100
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 73/100
petertriho/nvim-scrollbar#127 ·
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 83/100