<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">
<br>
</div>So, I had intended for the patch that I sent with the UI stuff to go in<br>
separately. It's much nicer for the version history if patches and<br>
changesets are small and self-contained. Since the UI stuff is not<br>
exactly small and also not specific to the UV5, I'd prefer it to be<br>
separate.<br></blockquote><div><br>No problem. Separate it will be. <br> <br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
That being said, I understand if it's harder for you to slice it up at<br>
this point. If you don't want to, and don't mind, I might try to do<br>
that before I apply the patch.<br></blockquote><div><br>I still have the original patch that you sent me. I would appreciate it if you add it since it is UI stuff? Do you need need me to email it back? I'll take care of of the uv5r part.<br>
</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im"><br>
> @@ -644,7 +644,7 @@<br>
> return int(version_tag[idx:idx+3])<br>
> raise Exception("Unrecognized firmware version string")<br>
><br>
> - def _get_settings(self):<br>
> + def get_settings(self):<br>
<br>
</div>You reverted one of my changes here, probably because I made it while<br>
you were working on this and it got merged into your patch without you<br>
realizing it. It would be good if you could avoid this, which may just<br>
be a bit of manual tweaking so that the code after your patch looks<br>
like the code before (minus your changes).<br>
<br>
The patch was:<br>
<br>
<a href="http://chirp.danplanet.com/projects/chirp/repository/revisions/5f4fff6266ab/diff" target="_blank">http://chirp.danplanet.com/projects/chirp/repository/revisions/5f4fff6266ab/diff</a><br></blockquote><div><br>Sorry. I don't remember how that came about. But I would be happy change what I have to not affect this. <br>
</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im"><br>
> + val1a = RadioSettingValueInteger(13600000, 52000000,<br>
<br>
</div>I know this isn't what you want to do, but at least it works. Maybe we<br>
should leave it as-is and I can help you make it format like a float<br>
after we get the core functionality into the tree.<br></blockquote><div><br>I think this great. I would like to get it to look like a float, though. It is really nice to have both VFOs set to a frequency after a programming session. <br>
</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
Otherwise, I think it looks good.<br>
<br>
Seriously, what's left to do? When can we start making fun of the folks<br>
that still use the icky OEM software? :)<br>
<span class="HOEnZb"><font color="#888888"></font></span><br></blockquote></div>I still have quite a few things on my list. I thought BCL would be a big hurdle. It turned out to be nothing more than a speed bump. I am very close to be able to say that there is no longer a need to use the OEM software.<br>
<br>Jim<br>