PatrickvL
PatrickvL
Calling this lib "virtx86" could be somewhat more accurate...
I couldn't find a contact address, so apologies in advance for abusing the issue tracker for this, but I'd like to point out an article that describes an optimal interpretation...
[ Replacement for accidentally closed PR #2228 ] This PR addresses #1604, introducing most of what's needed to support COLORSIGN, COLORKEYCOLOR, COLORKEYOP alongside with a small ALPHAKILL refactoring. To get...
## Quick summary Currently, when Cxbx-Reloaded is busy scanning symbols, no visual feedback is given. ## Details This might lead users to think emulating 'hangs', while in reality there actually...
Instead of everyone applying their own indenting style to Cxbx-Reloaded code via relatively small pull requests, update our entire code base to one style, in one go, without any other...
In order to support more controllers, like the Xbox 360 and possibly Xbox one controller, next to the original Xbox controller, switch the use of legacy DirectInput API to something...
Separate from [which visual component library we'll be using](https://github.com/Cxbx-Reloaded/Cxbx-Reloaded/issues/578), we must first have a solid design for our user-interface, before we can even consider implementing it. [A quick search](https://www.google.nl/search?q=emulator+gui&tbm=isch) shows...
Cxbx-Reloaded currently still uses `CreateThread()` and `TerminateThread()`. It may still be necessary to call `TerminateThread()` under some circumstances, but otherwise `ExitThread()` is the advised API to use. But according to...
Cxbx-Reloaded is currently using Windows API's. It's is build with Visual Studio. It uses many code constructs of MSVC. It's written in a (bad) mix of c and c++. It...
Instead of keeping around various issues on the preferred way of coding on cxbx, we should instead write up (and keep up to date) a coding guidelines document which stipulates...