On 12/30/2013 1:10 PM, Tom Hayward wrote:
It probably wouldn't be too involved to add a JSON output to RadioSettingGroup. You could run a diff on this. This makes some sense to me for power users, but not for accessibility.
To me, that would be cool and would address my needs even if it was only available after turning on the developer functions.
I've never seen this. I'm curious how settings are put in a table format. Key-value seems more natural.
Agreed, but since it fits the tool many people have available to them, I'm seen a bunch of software that outputs key value pairs as a 2-3 column table. To me I'm happy with any text that I can take a pass at with the text processing tools at my disposal, so JSON, tab separated, csv all good.
As Jens mentioned, there's other stuff in the radio img you don't want to blindly copy, like calibration data. I was suggesting copying only the known settings bytes. Since it's the same model, you can simply copy the settings blob without any conversion. The UI for this feature could simply be a checkbox under the frequency import table that says "also import settings?".
That sounds pretty reasonable.
Just curious, are radio's like the baofeng with different firmware versions considered the same model or different?