emulators
Emulators allow the host system to emulate the qualities of a client system. For example, a mobile application developer might run an emulated device on their PC in order to test how their application would perform and appear on an actual phone or tablet.
Here are 84 public repositories matching this topic...
Doxygen Comments referencing NetStructures should be changed to GameData
-
Updated
Sep 11, 2014 - C
-
Updated
Nov 3, 2020 - Shell
-
Updated
Dec 5, 2020 - Shell
-
Updated
Dec 20, 2020 - Rust
At the moment, the X86_64CoreRegs::regs field and X86[_64]CoreRegs::segments fields rely on an implicit ordering documented in their respective comments. It would be much better if explicit fields were used instead.
As pointed out in daniel5151/gdbstub#34 (comment), there is no "one true" ordering for these registers, which could result in some nasty bug
-
Updated
Mar 31, 2016 - HTML
-
Updated
Dec 26, 2020 - C
-
Updated
Dec 20, 2020 - Makefile
-
Updated
Dec 27, 2020 - C++
-
Updated
Mar 8, 2020 - Java
The emulator will open any given input file and attempt to run it as a Gameboy ROM. The cartridge header is not being checked at all.
The Cartridge header, as described here, is located from bytes 0x0100 to 0x014F and contains some game metadata. We need some code to validate this header, and also parse it neatly so that the metadat
Allow modified patches to be exported as IPS patches. Modified means that some of the patch records are unchecked in the patch records view.
-
Updated
Oct 28, 2020 - C++
-
Updated
Nov 5, 2020 - C#
-
Updated
Mar 19, 2020 - C++
-
Updated
Dec 30, 2018 - C++
-
Updated
Jul 11, 2020 - C
-
Updated
May 28, 2020 - Rust
-
Updated
Jun 4, 2020 - Rust
- Wikipedia
- Wikipedia


I recently ported my emulator to use pixels, and it's great! I love the automatic scaling to the window size.
However, I would also like to allow my users to select a scaling factor that they prefer, regardless of window size. I tried passing my own values to
pixels.resize, but this doesn't do what I want.