<html><body><div style="color:#000; background-color:#fff; font-family:HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif;font-size:16px"><div dir="ltr"><span>remove the decorator:</span></div><div dir="ltr" id="yui_3_16_0_1_1430227117620_4502"><span style="font-family: 'Helvetica Neue', 'Segoe UI', Helvetica, Arial, 'Lucida Grande', sans-serif; font-size: 13px;" class="" id="yui_3_16_0_1_1430227117620_4501">@directory.register</span><span><br></span></div><div dir="ltr" id="yui_3_16_0_1_1430227117620_4502"><span style="font-family: 'Helvetica Neue', 'Segoe UI', Helvetica, Arial, 'Lucida Grande', sans-serif; font-size: 13px;" class="">from the base class</span></div><br> <div style="font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; font-size: 16px;" id="yui_3_16_0_1_1430227117620_4495"> <div style="font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; font-size: 16px;" id="yui_3_16_0_1_1430227117620_4494"> <div dir="ltr" id="yui_3_16_0_1_1430227117620_4493"> <hr size="1"> <font size="2" face="Arial" id="yui_3_16_0_1_1430227117620_4492"> <b><span style="font-weight:bold;">From:</span></b> David Fannin <dfannin@sushisoft.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> Tuesday, April 28, 2015 12:04 AM<br> <b><span style="font-weight: bold;">Subject:</span></b> Re: [chirp_devel] [PATCH] This is the latest experimential version for the TYT-TH9000D radio driver<br> </font> </div> <div class="y_msg_container" id="yui_3_16_0_1_1430227117620_4503"><br><div id="yiv3678938055"><div dir="ltr" id="yui_3_16_0_1_1430227117620_4504">One other question before I send the next revision for the TH9000D radio.<div id="yui_3_16_0_1_1430227117620_4505"><br></div><div id="yui_3_16_0_1_1430227117620_4506">There are three versions of the same base radio (2 m , 220 and 440 Mhz versions) - They all share the same image file format and functions, except that they operate over different frequency ranges.</div><div id="yui_3_16_0_1_1430227117620_4507"><br></div><div id="yui_3_16_0_1_1430227117620_4508">I created a base class - Th9000Radio(), and then extend that class for each of the three models (e.g. Th9000144Radio(), etc) .</div><div id="yui_3_16_0_1_1430227117620_4509"><br></div><div id="yui_3_16_0_1_1430227117620_4510">The issue with this is that the base class shows up in menu selections as a valid radio, along with the other three versions.</div><div id="yui_3_16_0_1_1430227117620_4511">Is there any way to hide the base class? Yes, I could make the base class as one of the three versions, and only extend it twice for the other models, but that seemed a little klugy. Any recommendations?</div><div id="yui_3_16_0_1_1430227117620_4512"><br></div><div>thanks</div><div id="yui_3_16_0_1_1430227117620_4513"><br></div><div>Dave KK6DF</div><div id="yui_3_16_0_1_1430227117620_4514"><br></div><div><br></div></div><div class="yiv3678938055gmail_extra"><br><div class="yiv3678938055gmail_quote">On Sat, Apr 25, 2015 at 7:30 AM, Dan Smith <span dir="ltr"><<a rel="nofollow" ymailto="mailto:dsmith@danplanet.com" target="_blank" href="mailto:dsmith@danplanet.com">dsmith@danplanet.com</a>></span> wrote:<br><blockquote class="yiv3678938055gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><span class="yiv3678938055">> For the auto file identification, I was going to try looking at the<br>
> frequency ranges in the image file for identification. These are<br>
> non-overlapping between the three models, and they are in a fixed<br>
> location in the image file. Eg. The 144 mhz models has a settable<br>
> tx/rx range between 132 and 152 Mhz (or close to this), the 220 Mhz<br>
> model has 200-250 mhz, etc.<br>
><br>
> The file sizes are the same, AFAIK, for all three, so I can't use that<br>
> approach. The image files don't have a consistent or usable "id string"<br>
> to help identity them ( I did a od/hex dump and reviewed what's there),<br>
> at least for the two radios ( 2 meter and 220 mhz models) that I have.<br>
<br>
</span>Sure, I thought that you were indicating that you couldn't provide<br>
identification for this driver. Sounds like you should be able to use<br>
file size to rule all the other models out and use band limits to<br>
distinguish within the 9000 line among the sub-models, right?<br>
<br>
Thanks!<br>
<span class="yiv3678938055HOEnZb"><font color="#888888"><br>
--Dan<br>
<br>
</font></span><br>_______________________________________________<br>
chirp_devel mailing list<br>
<a rel="nofollow" ymailto="mailto:chirp_devel@intrepid.danplanet.com" target="_blank" href="mailto:chirp_devel@intrepid.danplanet.com">chirp_devel@intrepid.danplanet.com</a><br>
<a rel="nofollow" target="_blank" href="http://intrepid.danplanet.com/mailman/listinfo/chirp_devel">http://intrepid.danplanet.com/mailman/listinfo/chirp_devel</a><br>
Developer docs: <a rel="nofollow" target="_blank" href="http://chirp.danplanet.com/projects/chirp/wiki/Developers">http://chirp.danplanet.com/projects/chirp/wiki/Developers</a><br></blockquote></div><br></div></div><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>