* Window.cpp holds the MainWindow code, for managing the emulator window. * main.cpp just holds the entry point (main()) and global application-related stuff. We are far from done with the cleanup, so there's a lot of cruft around, but the basic idea is the following: I started by splitting main.cpp into separate files. Basically, the frontend code became a mess, and everything was more or less just dumped in the global namespace - there are some modules which live in their own namespaces, but it's all not very modular, and doesn't lend itself to running multiple instances of melonDS. Obviously, over time we added various features to the emulator, rebuilt the frontend around different UI toolkits, piled on more features, and so on. We had a simple window, a dedicated thread to run the actual emulation, and that was it. Originally, the frontend was just quickly built around the program entry point in main.cpp, as it just needed to provide a means to use the emulator. The frontend is proving to be tricky, because it was largely built without many regards for code quality. The goal is still the same: to adapt melonDS for supporting multiple instances within one process. Maybe I could have a sort of personal blog for non-melonDS projects of that kind, or just personal stuff in general.Ģ3 comments (last by inflatable yoshi) | Post a commentĪs I have received and set up my new laptop, I've been able to work on melonDS some. I've also been caught in a fun side project that involves reverse-engineering (and emulating, heh) ancient FPGAs. January has been rough for me, but things are getting better. Other than that, sorry for the lack of updates lately. I'm having a bit of a question there: if we got multiple windows, which one should have the OSD? The main window? The currently active one? All of them? This is not only part of the ongoing refactor, but would also pave the way for separate windows, a feature that has long been requested. There's still a whole pile of issues to fix, but it's looking promising so far. This is just a quick attempt at supporting multiple windows. 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.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |