Tl;dr — We implemented a change to fix a mouse cursor bug in the SDL2 library and open sourced it on Github.
Parsec uses the SDL2 library to handle most inputs and interactions between the remote interface and gaming PC. We ran into an issue with the library, however, as we were developing our Raspberry Pi client. The SDL2 mouse functions were a good start, but using the cursor as dynamically as Parsec does, a few cracks started to appear in the mouse functionality. Switching between relative and absolute mode caused the cursor to jump around. The “hot” point in the cursor was incorrect, eg the I-Beam was selecting with the upper left corner.
As part of our mission, we want to contribute to the open source community whenever we can. In this case, we had to implement a couple fixes to the SDL2 library. You can take a look at a few of the changes we made to SDL here. Beyond that, there was more subtle tweaking to HDMI frequencies and things of that nature to make Parsec what it is, but those were the big rocks on our way to getting the little $35 Pi to a place where you could play Witcher 3 on it.
More posts in Category
Build your perfect Parsec with our Teams API
We recently launched our Parsec for Teams API, making key admin functionality open & accessible to organizations who need it. It’s a big step on a...
Uncategorized
About our Series B and Parsec’s year of transformation
For most around the world, 2020 has been a year that at its absolute best was defined by deeply uncomfortable, previously unfathomable, transformation...
Uncategorized
Cloud Parsec & The Future of Online FGC Tournaments
All over the world, creatives are relying on Parsec and Parsec for Teams to keep media, entertainment, and, of course, games on track during the pande...
Uncategorized