Hi Tom ,Jens and Robert thanks for your thoughts :) my idea is to export RadioSetting list to a separate csv from memories one, the format can be:
setting key, setting description, field type, acceptable values, value
I will probably use tab instead of comma as field separator to avoid problems with string settings that allow commas in value. At import we can use only key and value to update each RadioSetting in list if the key exists and let the set_value method do the usual checks, at end we can show a dialog to let user know if there were any unknown key or unacceptable value.
This will obviously export/import only well known settings we already support using existing code do same validation done at user input. Being basically a text file the csv (i suppose) can be easily read by text2speech and edited with non visual editors. Someone can also remove some rows from the file to import only some of the settings and use it as a sort of "stock settings" (I think to people managing a fleet of radio or avoid importing any calibration setting from different radio).
I also like Tom's idea to import settings directly from img but this have in my opinion some limitation so i think we can go providing both cvs and img settings import.
Although you have expressed some (stimulating) criticism I dont see in this discussion any concrete reason for not try implementing it. I'll translate my idea in a patch in next days so you all can try it and probably better understand than from my english ;)
73 de IZ3GME Marco