-
-
Notifications
You must be signed in to change notification settings - Fork 175
Port key and mouse to SDL3 #3207
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM 👍
I wanted to test this, so I rebased against main and ran I got the following warnings-to-errors: ../src_c/mouse.c(100): error C2220: the following warning is treated as an error
../src_c/mouse.c(100): warning C4244: '=': conversion from 'int' to 'float', possible loss of data
../src_c/mouse.c(101): warning C4244: '=': conversion from 'int' to 'float', possible loss of data
../src_c/mouse.c(109): warning C4244: '=': conversion from 'int' to 'float', possible loss of data
../src_c/mouse.c(113): warning C4244: '=': conversion from 'int' to 'float', possible loss of data
../src_c/mouse.c(118): warning C4244: 'function': conversion from 'float' to 'int', possible loss of data
../src_c/mouse.c(118): warning C4244: 'function': conversion from 'float' to 'int', possible loss of data
../src_c/mouse.c(149): warning C4244: 'function': conversion from 'float' to 'int', possible loss of data
../src_c/mouse.c(149): warning C4244: 'function': conversion from 'float' to 'int', possible loss of data
../src_c/mouse.c(253): warning C4244: '=': conversion from 'SDL_WindowFlags' to 'Uint32', possible loss of data |
8bf0cd7
to
f1e61a6
Compare
I have rebased this branch on main and force pushed. Previously I didn't see these warnings on CI but lets see how things go now UPDATE: Could reproduce those fails on CI, so force pushed again with fixes for that |
f1e61a6
to
634619b
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let's merge it in
Just following the footsteps of #3206 but separated out in a different PR because these changes are not as trivial as those