<html><body><div style="color:#000; background-color:#fff; font-family:tahoma, new york, times, serif;font-size:12pt"><div><span>So maybe you can help me clear up the setting logic.</span></div><div style="color: rgb(0, 0, 0); font-size: 16px; font-family: tahoma, 'new york', times, serif; background-color: transparent; font-style: normal; "><span>Is set_memory called for every channel at some point, or only when channels are "touched" (i.e., some control event fired in ui)?</span></div><div style="color: rgb(0, 0, 0); font-size: 16px; font-family: tahoma, 'new york', times, serif; background-color: transparent; font-style: normal; "><span><br></span></div><div style="color: rgb(0, 0, 0); font-size: 16px; font-family: tahoma, 'new york', times, serif; background-color: transparent; font-style: normal; "><span>How exactly would chirp deal with a channel imported w/ 6.25 step, if it is not in my valid_tuning_steps?</span></div><div style="color: rgb(0, 0,
0); font-size: 16px; font-family: tahoma, 'new york', times, serif; background-color: transparent; font-style: normal; "><span>Would it leave tuning_step empty?</span></div><div style="color: rgb(0, 0, 0); font-size: 16px; font-family: tahoma, 'new york', times, serif; background-color: transparent; font-style: normal; "><span><br></span></div><div style="color: rgb(0, 0, 0); font-size: 16px; font-family: tahoma, 'new york', times, serif; background-color: transparent; font-style: normal; "><span>So i fixed my tones with this:</span></div><div style="color: rgb(0, 0, 0); font-size: 16px; font-family: tahoma, 'new york', times, serif; background-color: transparent; font-style: normal; "><span><div style="background-color: transparent; ">TONES = list(chirp_common.TONES)</div><div style="background-color: transparent; ">for tone in [ 165.5, 171.3, 177.3 ]:</div><div style="background-color: transparent; "><span class="Apple-tab-span"
style="white-space:pre"> </span>TONES.remove(tone)</div><div style="background-color: transparent; color: rgb(0, 0, 0); font-size: 16px; font-family: tahoma, 'new york', times, serif; font-style: normal; "><br></div><div style="background-color: transparent; color: rgb(0, 0, 0); font-size: 16px; font-family: tahoma, 'new york', times, serif; font-style: normal; ">But I dont see anywhere to tell chirp about this new list, such returning a RadioFeatures.valid_tones, etc in get_features.</div><div style="background-color: transparent; color: rgb(0, 0, 0); font-size: 16px; font-family: tahoma, 'new york', times, serif; font-style: normal; ">Should I be mutating chirp_commons.TONES directly?</div><div style="background-color: transparent; color: rgb(0, 0, 0); font-size: 16px; font-family: tahoma, 'new york', times, serif; font-style: normal; "><br></div><div style="background-color: transparent; color: rgb(0, 0, 0); font-size: 16px; font-family: tahoma, 'new
york', times, serif; font-style: normal; "><br></div></span></div><div><br></div> <div style="font-family: tahoma, 'new york', times, serif; font-size: 12pt; "> <div style="font-family: 'times new roman', 'new york', times, serif; font-size: 12pt; "> <div dir="ltr"> <hr size="1"> <font size="2" face="Arial"> <b><span style="font-weight:bold;">From:</span></b> Dan Smith <dsmith@danplanet.com><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> Sunday, August 25, 2013 5:24 PM<br> <b><span style="font-weight: bold;">Subject:</span></b> Re: [chirp_devel] [FT-90] add initial support for FT-90R. #1087<br> </font> </div> <div class="y_msg_container"><br>> I'm currently working on mapping out the special channels (vfos,<br>> calls, u/l scan limits) as well as the some of the global settings.<br>> I'm not sure exactly how those special channels are
dealt with, as I<br>> didnt see a sample implementation in template, just an actual<br>> implementation like ft-857, etc.<br><br>Yeah, that's unfortunately pretty ugly right now. Looking at one of the<br>other implementations will get you there.<br> <br>> How can I solve the issues with importing from floats that dont match<br>> (i.e., 6.25)? do I need to bracket them into my list at get_memory or<br>> set_memory time?<br><br>What do you mean? If you don't declare that you support 6.25kHz splits<br>then CHIRP won't ask your driver to attempt to set one.<br> <br>> On the ToneSql type, how do I preserve a channel setting for Bell or<br>> Auto, if chirp doesnt support it. Do I have to be destructive and box<br>> all channels into one of the supported types? It's totally possible<br>> to have set Bell or Auto in memory on the radio. What happens when I<br>> import this now? How should I deal with this, if I cant tell
chirp<br>> what are possible/legal values for my radio?<br><br>Right now, we just coerce those to supported values, which ends up<br>losing the bell setting if the user attempts to write to that memory<br>channel. You could, I suppose, detect and preserve that bit prior to<br>setting it if you want, but then the user would have to disable an<br>errant bell bit on the radio itself. You could expose that in the extra<br>settings...<br><br>> I commented out the ARS code, but now if I can do custom fields (i'll<br>> see how it's done with uv-5r) then I may be able to make this a bool<br>> field, and deal with the logic of ignoring/setting duplex field in<br>> get/set memory members.<br><br>Cool.<br> <br>> I understand it is semantics and style, but since<br>> these allowed tone values for this particular radio will NEVER<br>> change, I don't want to be dependent upon chirp_common tones never<br>> changing.<br><br>I understand it's
a bit icky, but we've done okay for five years on<br>this model.<br><br>> It would be a long shot that they ever do change, but if<br>> they do, it would be more difficult to determine which tones are now<br>> supported/unsupported, since the "source of truth" gets altered.<br><br>I understand. The reason we started with this pattern pre-dates CHIRP<br>supporting anything but Icom radios, and a few other things. It's all<br>in git history and the subtractive model makes it easier to eye-parse<br>the differences.<br><br>Thanks!<br><br>-- <br>Dan Smith<br>www.danplanet.com<br>KK7DS<br>_______________________________________________<br>chirp_devel mailing list<br><a ymailto="mailto:chirp_devel@intrepid.danplanet.com" href="mailto:chirp_devel@intrepid.danplanet.com">chirp_devel@intrepid.danplanet.com</a><br><a href="http://intrepid.danplanet.com/mailman/listinfo/chirp_devel"
target="_blank">http://intrepid.danplanet.com/mailman/listinfo/chirp_devel</a><br>Developer docs: <a href="http://chirp.danplanet.com/projects/chirp/wiki/Developers" target="_blank">http://chirp.danplanet.com/projects/chirp/wiki/Developers</a><br><br></div> </div> </div> </div></body></html>