You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
First of all, thank you for creating and maintaining raylib—it's an amazing library that makes graphics programming fun and accessible!
While working on a project using raylib with the DRM backend (PLATFORM=DRM), I noticed that the DRM backend currently supports:
Only 1 mouse
Only 1 keyboard
A limited, configurable number of gamepads (default: 4).
To address this, I myself implemented dynamic support for multiple mouse and keyboard devices in a custom Raylib source. My approach involved:
Making mouseFd and keyboardFd pointers to dynamically allocated arrays.
Using RL_REALLOC to adjust the array size as new devices are configured.
I would like to clarify if the current limitation on device counts is intentional or simply a design decision. Additionally, I’m considering creating a pull request for this enhancement and would like feedback on whether it would be desirable. Specifically:
Should I implement this dynamic support for all devices (mouse, keyboard, gamepads)?
Or should I implement fixed, configurable amount for mouse and keyboard like gamepads are implemented
Are there specific concerns or guidelines I should be aware of?
Environment
Operating System: Arch Linux
Platform Backend: DRM
Other details are likely not relevant to this issue but can be provided if necessary.
The text was updated successfully, but these errors were encountered:
I'm sure that GLFW does support multiple mouse and keyboard, it just can't distinguish them, this what your ref's say. Maybe there was a misunderstanding. I didn't ask for support to distinguish which mouse or keyboard is being used, the DRM backend polls only the last device it finds for each category (mouse, keyboard) except the gamepads which have a limited but configurable amount. And I wanted to know if this is intentional or should be changed. And regarding pointers they will only be used internally when polling so it won't change any APIs.
raysan5
changed the title
[rcore_drm] Adding support for more than one keyboard/mouse
[rcore][drm] Adding support for more than one keyboard/mouse
Dec 23, 2024
Please, before submitting a new issue verify and check:
Issue description
First of all, thank you for creating and maintaining raylib—it's an amazing library that makes graphics programming fun and accessible!
While working on a project using raylib with the DRM backend (PLATFORM=DRM), I noticed that the DRM backend currently supports:
To address this, I myself implemented dynamic support for multiple mouse and keyboard devices in a custom Raylib source. My approach involved:
I would like to clarify if the current limitation on device counts is intentional or simply a design decision. Additionally, I’m considering creating a pull request for this enhancement and would like feedback on whether it would be desirable. Specifically:
Environment
Operating System: Arch Linux
Platform Backend: DRM
Other details are likely not relevant to this issue but can be provided if necessary.
The text was updated successfully, but these errors were encountered: