<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Fri, Jan 31, 2014 at 9:43 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"><div class="im"><br></div>
<div class="im"><br>
> I've ripped out 99% of the structure and code from the uv5r.py that<br>
> isn't used or necessary. I've also borrowed from other radios as well as<br>
> cleaned up the code from what I've learn by 'hacking' on the uv5r.py<br>
> file for the last 13 months.<br>
<br>
</div>Ripped out 99% of the non-overlapping code or 99% of the UV5 code entirely?<br>
<div class="im"><br></div></blockquote><div><br></div><div>What I meant was that if there were 100 lines of code that was not used for the UV-6, I have only removed 99 lines of it. I haven't removed the code for adjusting the band limits or the power-on messages yet. Sorry for the confusion.</div>
<div><br></div><div>I was trying to look over every settings to see if it could be utilized by the radio. I didn't want to remove it just because the OEM software didn't have it. If is still did something that the could be utilized by the user/radio, I wanted to leave it in.</div>
<div><br></div><div>If the UV-6 was going to be supported by a separate uv6.py driver, which was my goal, then I wanted to be sure it was completely sanitized from any unnecessary UV-5R, F-11, UV-82 and some left over BJ-UV-55 code in the structure or anywhere else.</div>
<div><br></div><div>What I was trying to avoid was to add it in and then find out it needed to be separate like the UV-55.</div><div><br></div><div>Jim</div><div><br></div></div></div></div>