3 ms·
Author here. The most recent change is that I started adding debugging UIs to the emulators, using the excellent Dear ImGui (https://github.com/ocornut/imgui ht
by flohofwoe 8y ago
Author here. The most recent change is that I started adding debugging UIs to the emulators, using the excellent Dear ImGui (https://github.com/ocornut/imgui https://github.com/ocornut/imgui).
The UI is in a separate version of the emulator, launched with the little "UI" button in the top right corner of the image panels (e.g. https://floooh.github.io/tiny8bit/kc85-ui.html?type=kc85_4 https://floooh.github.io/tiny8bit/kc85-ui.html?type=kc85_4).
The UI is updated once per 60Hz frame, so you only see a per-frame snapshot of the microchip pins which on its own isn't that useful yet except for a nice blinkenlight effect, but it will make a lot more sense once a step-debugging window is added. This will let you inspect the pins after each CPU instruction (still not as accurate as the emulation, which is running with machine-cycle granularity on Z80, and clock-cycle granularity on 6502 machines.
The emulators are written in C(99), with some platform-specific bits written in Objective-C and Javascript, and in C++ for the UI parts (since Dear ImGui is implemented in C++). Apart from the WebAssembly version, Win32, Linux, OSX and iOS is also supported, but you need to compile those yourself :)
- titzer 8y agoThis is super cool! And it's awesome that it uses WebAssembly.
- FullyFunctional 8y agoThis is incredible. I first thought it was just screenshots. Anyway to contact you offline? I want to suggest Nascom 2 support.