The latter provides a means to display the emulator's video output and lets the user interact with the emulator, the former feeds the inputs into the melonDS core, runs it and manages it. Historically, the frontend was structured around one emu thread and one emu window. On the frontend side, we need to add support for multiple different emulator windows. But atleast, the biggest part of the work is done. It's also likely not perfect, we will likely have to do more work to clean up and harmonize the codebase. I will need a while to adjust to the new changes that have been done to the melonDS core. On my side, I (finally) ordered a new laptop, so I'm waiting to receive it and set it up before I do more big work on melonDS. The frontend code is now going to need adequate refactoring too. JesseTG mostly finished the work on the core, so that's one big thing out of the way. What's new since the last post? I had started working on refactoring the melonDS codebase for the ambitious changes to come. Hopefully it's going to get better with the Christmas holidays. If you're running into trouble: Howto/FAQ (WIP) Wifi: local multiplayer, online connectivity.Various display position/sizing/rotation modes.Nearly complete core (CPU, video, audio.While it is still a work in progress, it has a pretty solid set of features: MelonDS aims at providing fast and accurate Nintendo DS emulation.
