<html><body><div style="color:#000; background-color:#fff; font-family:HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif;font-size:10pt"><div><span><br></span></div><div>Im not sure if you are getting at this, but one "dirty little secret" of importing images into other "identical" radios is that,</div><div>in at least some models, there may be other non-exposed settings (e.g., power calibrations, deviations, level settings, etc) that are stored in the radio image,</div><div>and are (or should be) specific to exactly that individual radio. While they _might_ be mostly portable between same model of radios, there could be potential issues.</div><div><br></div><div style="color: rgb(0, 0, 0); font-size: 13px; font-family: HelveticaNeue, 'Helvetica Neue', Helvetica, Arial, 'Lucida Grande', sans-serif; background-color: transparent; font-style: normal;">The best approach should be to import export channels and settings directly from
existing image, rather than opening the image and uploading it directly to the radio.</div><div style="color: rgb(0, 0, 0); font-size: 13px; font-family: HelveticaNeue, 'Helvetica Neue', Helvetica, Arial, 'Lucida Grande', sans-serif; background-color: transparent; font-style: normal;">This is up to the user to do this, but currently I doubt most users understand this, nor is it really documented anywhere (that Im aware of).</div><div style="color: rgb(0, 0, 0); font-size: 13px; font-family: HelveticaNeue, 'Helvetica Neue', Helvetica, Arial, 'Lucida Grande', sans-serif; background-color: transparent; font-style: normal;"><br></div><div style="color: rgb(0, 0, 0); font-size: 13px; font-family: HelveticaNeue, 'Helvetica Neue', Helvetica, Arial, 'Lucida Grande', sans-serif; background-color: transparent; font-style: normal;">The "ability to import settings from existing images of same model of radio" should be the new functionality here. I think Tom
mentioned this and I vote for this approach.</div><div style="color: rgb(0, 0, 0); font-size: 13px; font-family: HelveticaNeue, 'Helvetica Neue', Helvetica, Arial, 'Lucida Grande', sans-serif; background-color: transparent; font-style: normal;"><br></div><div style="color: rgb(0, 0, 0); font-size: 13px; font-family: HelveticaNeue, 'Helvetica Neue', Helvetica, Arial, 'Lucida Grande', sans-serif; background-color: transparent; font-style: normal;">-J</div> <div style="font-family: HelveticaNeue, 'Helvetica Neue', Helvetica, Arial, 'Lucida Grande', sans-serif; font-size: 10pt;"> <div style="font-family: HelveticaNeue, 'Helvetica Neue', Helvetica, Arial, 'Lucida Grande', sans-serif; font-size: 12pt;"> <div dir="ltr"> <hr size="1"> <font size="2" face="Arial"> <b><span style="font-weight:bold;">From:</span></b> Robert Terzi <rct@r-t.org><br> <b><span style="font-weight: bold;">To:</span></b> chirp_devel@intrepid.danplanet.com <br> <b><span
style="font-weight: bold;">Sent:</span></b> Monday, December 30, 2013 11:36 AM<br> <b><span style="font-weight: bold;">Subject:</span></b> Re: [chirp_devel] RFC settings import export<br> </font> </div> <div class="y_msg_container"><br>On 12/30/2013 1:03 AM, Tom Hayward wrote:<br clear="none"><br clear="none">> It makes more sense to me to begin by supporting Import/Export of<br clear="none">> settings via img from identical radio models. For example, import<br clear="none">> uv5r.img into another uv5r. For this you will not need any CSV<br clear="none">> encoding or translation between models. I think this feature would<br clear="none">> satisfy most user's need for settings import.<br clear="none"><br clear="none">Couldn't that use case of moving settings to an identical radio already<br clear="none">be handled by just using the source image after importing the frequencies<br clear="none">from the destination radio's image?<br
clear="none"><br clear="none">The recently requested use case was the possibility of improved accessibility<br clear="none">for the visually impaired by allowing CSV export and import. As mentioned, this<br clear="none">would need 100% fidelity in the export and re-import to be useful, so would be<br clear="none">difficult to achieve, especially with CSV.<br clear="none"><br clear="none">The use case that I haven't seen mentioned, is exporting to some textual<br clear="none">representation to facilitate settings comparisons. This is useful for<br clear="none">not only comparing two radios, but also for determining what settings have<br clear="none">changed over time on a single radio. I use G4HFQ's FTBVX8 software in that<br clear="none">manner. The settings user interface is table oriented and can be exported<br clear="none">to text files making compares possible, even on radios with a lot of settings<br clear="none">like the
VX-8.<br clear="none"><br clear="none">As this can be very useful for diagnostic purposes, I'd be interested in seeing<br clear="none">some sort of textual export/report, even if there were no import, initially just an<br clear="none">additional developer function. More of the settings meta data would need to be exposed,<br clear="none">which would wind up providing additional documentation for each radio's settings.<br clear="none">I'm guessing that is where Jens J. is headed recently asking about doc strings for settings.<br clear="none"><br clear="none">Just adding my thoughts, the subject did say this was a request for comments, right?<br clear="none"><br clear="none">A happy and healthy New Year to all,<br clear="none">--Rob<div class="yqt1345483760" id="yqtfd89833"><br clear="none"><br clear="none">_______________________________________________<br clear="none">chirp_devel mailing list<br clear="none"><a shape="rect"
ymailto="mailto:chirp_devel@intrepid.danplanet.com" href="mailto:chirp_devel@intrepid.danplanet.com">chirp_devel@intrepid.danplanet.com</a><br clear="none"><a shape="rect" href="http://intrepid.danplanet.com/mailman/listinfo/chirp_devel" target="_blank">http://intrepid.danplanet.com/mailman/listinfo/chirp_devel</a><br clear="none">Developer docs: <a shape="rect" href="http://chirp.danplanet.com/projects/chirp/wiki/Developers" target="_blank">http://chirp.danplanet.com/projects/chirp/wiki/Developers</a><br clear="none"></div><br><br></div> </div> </div> </div></body></html>