Re: [chirp_devel] Proposal to make use of TSQL in csv import friendlier

On Apr 22, 2014 12:49 PM, chirp.cordless@xoxy.net wrote:

But I'd like to propose a very specific change to csv import, such that if exactly one of the columns rToneFreq and cToneFreq exists in the csv file, that the value in that column be used for both rtone and ctone.

Makes sense to me. The rTone value is a much more useful default than 88.5.

This could probably be done in import logic, not CSV.

Tom KD7LXL