In fact, they way PI handles 'multiple instances' can be extremely useful.
First, if you really want to start a second instance with an 'identical' setup to the first instance, it is a simple case of editting the config file to 'duplicate' the complete section for the 'first instance' and to then rename it as the 'second instance'
Then, once you open the second instance, any configuration changes are saved (on closure of the second instance) in the second section of the configuration file.
What would be EXTREMELY USEFUL is the ability to open a new instance of PI, but to specifically tell PI which configuration profile to use. That way, the user has simplistic 'ultimate' control. In fact, could a running instance of PI be forced to go and 'get' a specific configuration file section? Could you 'save' the running PI configuration into the config file with a specific 'section identifier'?
Juan - your thoughts?
Cheers,