ConfigParser

[borrob]

Every time you start a CodeKlavier session, you have put in the midi-instrument and the settings and stuff. Let's use configparser for that!

Suggested workflow:

• starting CodeKlavier will ask you to give the filename for the configfile.
• leave blank to use the default
• add a 'configFileCreator' to write an appropriate configfile and save it

[narcode]

Yes, this definitely has to be introduced, specially in cases when u are re-starting the system constantly. i.e. test phases.

For the workflow though, i prefer the idea of adding arguments in the commandline, so if it's blank it grabs the default configfile $ ./motippets.py

It if has the argument it grabs a specific file: $ ./motippets.py -c myfile.config

This way we could scale it to have more options through the command line. $ ./motippets.py -m newconfigfilemake.config

I will make a new branch for this enhancements. It will be called 0.2.1...

[narcode]

cool @borrob Thanks for the fast response. Your contribution was merged! 🚀