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
Key forwarding (used for rp2040-doom) seems to work fine for as long as there's a continous stream of keypresses to send. After a short inactivity, my client always closes.
Poking it with the big stick my almost non-existent programming abilities are, I found the SDL_WaitEvent() becoming false after a short inactivity - so I removed it from the while-loop's condition's AND and put it into the loop:
`old: //while (!done && SDL_WaitEvent(&event)) {
new: while (!done) {
SDL_WaitEvent_return = SDL_WaitEvent(&event);`
At least, this way it now seems to keep working and doesn't close after short inactivity.
There might, of course, be much better (or more correct) ways to solve this issue than this amateurish hack (and maybe it's even caused by something completely unrelated) - but at least it did fix my issue with it :)
This just in case anyone else is seeing a similar issue (or has a better way of fixing this).
The text was updated successfully, but these errors were encountered:
Key forwarding (used for rp2040-doom) seems to work fine for as long as there's a continous stream of keypresses to send. After a short inactivity, my client always closes.
Poking it with the big stick my almost non-existent programming abilities are, I found the SDL_WaitEvent() becoming false after a short inactivity - so I removed it from the while-loop's condition's AND and put it into the loop:
`old: //while (!done && SDL_WaitEvent(&event)) {
new: while (!done) {
SDL_WaitEvent_return = SDL_WaitEvent(&event);`
At least, this way it now seems to keep working and doesn't close after short inactivity.
There might, of course, be much better (or more correct) ways to solve this issue than this amateurish hack (and maybe it's even caused by something completely unrelated) - but at least it did fix my issue with it :)
This just in case anyone else is seeing a similar issue (or has a better way of fixing this).
The text was updated successfully, but these errors were encountered: