remove the decorator:
@directory.register
from the base class

From: David Fannin <dfannin@sushisoft.com>
To: chirp_devel@intrepid.danplanet.com
Sent: Tuesday, April 28, 2015 12:04 AM
Subject: Re: [chirp_devel] [PATCH] This is the latest experimential version for the TYT-TH9000D radio driver

One other question before I send the next revision for the TH9000D radio.

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.

I created a base class - Th9000Radio(), and then extend that class for each of the three models (e.g. Th9000144Radio(), etc) .

The issue with this is that the base class shows up in menu selections as a valid radio, along with the other three versions.
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?

thanks

Dave KK6DF



On Sat, Apr 25, 2015 at 7:30 AM, Dan Smith <dsmith@danplanet.com> wrote:
> For the auto file identification, I was going to try looking at the
> frequency ranges in the image file for identification.  These are
> non-overlapping between the three models, and they are in a fixed
> location in the image file.   Eg.   The 144 mhz models has a settable
> tx/rx range between 132 and 152 Mhz (or close to this), the 220 Mhz
> model has 200-250 mhz, etc.
>
> The file sizes are the same, AFAIK, for all three, so I can't use that
> approach.  The image files don't have a consistent or usable "id string"
> to help identity them ( I did a od/hex dump and reviewed what's there),
> at least for the two radios ( 2 meter and 220 mhz models) that I have.

Sure, I thought that you were indicating that you couldn't provide
identification for this driver. Sounds like you should be able to use
file size to rule all the other models out and use band limits to
distinguish within the 9000 line among the sub-models, right?

Thanks!

--Dan


_______________________________________________
chirp_devel mailing list
chirp_devel@intrepid.danplanet.com
http://intrepid.danplanet.com/mailman/listinfo/chirp_devel
Developer docs: http://chirp.danplanet.com/projects/chirp/wiki/Developers


_______________________________________________
chirp_devel mailing list
chirp_devel@intrepid.danplanet.com
http://intrepid.danplanet.com/mailman/listinfo/chirp_devel
Developer docs: http://chirp.danplanet.com/projects/chirp/wiki/Developers