<div dir="ltr">One other question before I send the next revision for the TH9000D radio.<div><br></div><div>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><br></div><div>I created a base class - Th9000Radio(), and then extend that class for each of the three models (e.g. Th9000144Radio(), etc) .</div><div><br></div><div>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>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><br></div><div>thanks</div><div><br></div><div>Dave KK6DF</div><div><br></div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Sat, Apr 25, 2015 at 7:30 AM, Dan Smith <span dir="ltr"><<a href="mailto:dsmith@danplanet.com" target="_blank">dsmith@danplanet.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">> 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="HOEnZb"><font color="#888888"><br>
--Dan<br>
<br>
</font></span><br>_______________________________________________<br>
chirp_devel mailing list<br>
<a 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></blockquote></div><br></div>