Sam Lantinga
Sam Lantinga
Yes, this looks good. If this functionality is merged, would you still need SDL_HINT_MOUSE_RELATIVE_CURSOR_VISIBLE and SDL_HINT_MOUSE_RELATIVE_CLIP_INTERVAL?
I'm inclined to accept this PR. It allows the application more flexibility listening to raw mouse deltas and is the only way for it to get them when SDL has...
> Exposing the raw data like this is a good idea, I think. Is this meant to be Windows only, or can we wire this up for things like Xinput2...
> 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...
If we are passing through the native data, then we should probably use floats. The GCMouseInput deltas definitely have sub-pixel precision, and if we want to adhere to your reasoning,...
> @slouken Would this fall under the purview of ABI lock-in or just API? This is new functionality, so it can be added anytime.
What language binding are you working on and how will this be consumed?
I'm not a fan of adding this to the headers. If we need this information, I'd rather it be annotated somewhere in src/dynapi. @icculus, thoughts?
This would be pretty reasonable to add, possibly with the new GPU API? I'm going to add this to the SDL 3.0 milestone for review.
Reading over the referenced PR, it looks like adding this will only add one additional entry point to the API, and is something we can add later, if bilinear filtering...