yeah, i had a look at it and was thinking of using Agar as a last resort. i am still inclined to work with the DrNokSnes approach.

i tested saving and restoring state on the emulator last night and it works fine. all i need now is a way to communicate between a separate app, say in Qt for all the menu options etc, and the emulator itself so that each knows when to stop and continue when the other is done.

i'm guessing the Qt app will be the entry point to the emulator. it then fires up the emulator once all configuration is done. however, i have yet to figure out how to get the emulator to return control back to the Qt app when the user wants to change some configuration.

i was thinking of sending a kill signal to the emulator (the emulator already has an option to save state when it exits gracefully) from the Qt app and leaving the Qt app running all the while. but i do need to be able to differentiate between a user exiting the emulator and a user wanting to make a change in the config. not impossible as i have a rough idea of how to do this already with exit codes.