Enhance Import/Export.

What is the current behaviour and why should it be changed?

Jamulus uses an .ini file to save session and configuration information. However for one who wishes to use different context or computers, the same Jamulus.ini file cannot be re-used without manual editing, which is not recommended.

Currently Import /Export functionality only allows the transfer of <stored... statements (i.e. fader related information) from one jamulus.ini file to another. When adding configurations or computers, it would be better if other shareable informations could also be transfered. At least, one such information regards the <ipaddress... statements.

Remedying this would facilitate usage from one configuration to another by sharing what is otherwise laborious to recreate with entry facilities or awaiting session conditions to replicate.

Describe possible approaches

A solution would be to add the <ipaddress... statements to the one that can be transferred by Import/Export.

I think this would be easy to implement and possibly transparent to previous version if they don't consider an import file with <ipaddress.. info as a wholly corrupted file ; hopefully , older versions would process only statements they understand.

Has this feature been discussed and generally agreed?

Discussion/Technical Suport & Help : Copy jamulus.ini from Windows unto Linux ? #2807

Beginne damit, Jamulus’ bestehende Import-/Export-Behandlung für jamulus.ini zu lokalisieren und vergleiche, wie <stored...>-Anweisungen im Vergleich zu <ipaddress...>-Anweisungen verarbeitet werden. Überprüfe anschließend den Kontext in issue #2807 und verifiziere, dass das Importieren und Exportieren die relevanten IP-Adress-Einträge bewahrt, ohne vorhandene Dateien zu beschädigen.