-
Notifications
You must be signed in to change notification settings - Fork 1.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[SDL2 Vita] Wrong touch IDs gets assigned to touch devices #9830
Comments
Please feel free to submit a PR to fix this, thanks! |
I'll do, but right now I'm out of home, first off I should test out this on my end. I'll be back when I get my home. |
Hello!
Now, I going to perform this. Actually very small tweak, just few digits, so long time of wait... |
@slouken, is possible that change I did will come into the next bugfix update? Or you already going to release the 2.32.0 very soon? I asking because of milestone where this task is. It's solved right now. |
Yes, I've merged it to release-2.30.x so it'll be in the next 2.30 release. |
- Begining of device ID with 0 violates the SDL's specification that means the 0 is an error, invalid, failure, etc. But on Vita here it's an actual device... - Replacing 0 and 1 with 1 and 2 to resolve this violation. (cherry picked from commit dd6c663)
Hello!
I do see that at the SDL2 touch device IDs gets assigned incorrectly: one of IDs had been assigned as 0 that results an invalid behaviour: the SDL_GetTouchDevice() claims the 0 is an invalid device, but in a case of Vita's code it's a fully valid device.
Anyway, on SDL3 side I see these device ID codes are valid.
The text was updated successfully, but these errors were encountered: