sukiletxe
commented
5 years ago Thanks for the issue, I'll take this into account.
However, some things must be clarified for this project:
I have three projects with similar goals (process input of some kind and output them using a synthesizer). These projects were started when I had some idea on how to use submodules but didn't usethem because I couldn't be bothered to learn, so nowthey are in varying states of phosilization, effectively sharing some parts of code but having mutations in other parts (deps, build process and code). So I still have to think about what to do next. My plan is to merge the three of them with a rewrite from scratch and without copying deps (or doing so as little as possible).
Whatever I decide, it should be done in July at a minimum, as I have exams and work to do in the meantime, and if I start now I'll get distracted (anyone familiar with procrastination with unimportant but kind of fun things?)
Leaving this open for now.
This emulator might be opened by double-clicking directly on the executable file without passing any parameters. To achieve this, a configuration file may be required. The configobj module is a good choice for this task. The command line arguments should override the parameters specified in the config file. For example, if port com5 is specified in the file and I pass com8 as a parameter, the program should use com8. Some suggestions for that:
If you implement these changes, this emulator will be almost ready for my next issue (not created yet): running as a Windows service without unneeded console windows.