expikr
The primary motivation for this is the ability to receive raw device counts while staying in non-relative mode. An example use-case is a twitch-action MOBA demanding low-latency hardware cursor (ruling...
For SDL2, both are still required as workaround since it won’t have the new rawinput subsystem. For SDL3, I’d still like to have the option of manual cursor visibility management...
Also I should probably add a button event counterpart to the raw channel, since mixing WM_MOUSE* button events with an asynchronous thread will result in out-of-sync ordering of button presses...
@Kontrabant I have implemented a hybrid approach: - raw axis readings are supplied as int - associated denominators for each axis are supplied as float This way, platforms with floating...
How frequent are SDL3 preview releases? Can't wait to pin to a release that has this.
Ctrl+L is burned into my muscle memory for doing everything in the browser. Or for some that would be Ctrl+K, which also matches VSCode.
Specifically PID0226/PID0227/PID0243 of VID1532, see [this discussion.](https://old.reddit.com/r/GlobalOffensive/comments/1e8lt8t/optimum_demos_the_new_snap_tap_and_shows_how/) As I said, the functionality is currently achievable via a downstream implementation, but imposes significant overhead to check on every event in the...
I think you misunderstood, closing is a bit hasty when the points haven't been clarified. I am talking about the SDL event queue, has nothing to do with blocking at...
The onus is on the game designer to communicate incompatibility and make the experience palatable. This proposal is purely about giving developers the ability to define "incompatible devices" and prevent...
Consider also the use case of a whitelist. Say I'm writing software for a specific medical device with SDL, which also communicates via HID but has device-specific behaviour that I...