<div dir="ltr">Hi,<div><br></div><div style>I've attached a revised patch.</div><div style><br></div><div style>Band plans (chirp/bandplan_*.py) contain some information to help with maintenance (source URL, version) and after that they are basically flat lists of Band instances. Band instances can suggest modes, tuning steps, tones, duplex offsets, etc. You can reuse one band plan in another using the + operator (eg. bandplan_na imports bandplan_iaru_r2)</div>
<div style><br></div><div style>chirp/bandplan.py defines the Band class and the BandTree class. These are distinct because the same Band may be in multiple BandTrees. A BandTree is just an optimised way of applying properties of wider bands to sub bands within them, as implemented in the search() function.</div>
<div style><br></div><div style>chirpui/bandplans.py handles all of the band plans on behalf of the user interface. When you add a band plan you just create bandplan_whatever.py and then add it to this file.</div><div style>
<br></div><div style>chirpui/mainapp.py has been modified to make channel defaults selection a pop up with a single select drop down (populated from chirpui/bandplans.py). To simplify conflict resolution I've flipped from multiple selection to single selection. I figure that if you go from adding amateur channels to adding marine channels you can select a different band plan when you start on the marine channels.</div>
<div style><br></div><div style>Users won't notice any immediate change except that the default (North America) now has some HF band defaults (eg. AM mode for 14.29MHz)</div><div><br></div></div><div class="gmail_extra">
<br><br><div class="gmail_quote">On Wed, Mar 13, 2013 at 1:05 PM, 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">> Yes, however a North American Marine band plan and a North American<br>
> Amateur band plan would both be under an ITU region 2 band plan, and<br>
> you might want to use both.<br>
<br>
</div>Hrm, bummer, okay.<br>
<div class="im"><br>
> You're right. I'll try it with objects and see how it looks. I<br>
> expect that will make it easier to calculate and claim the repeater<br>
> input blocks too (with opposite offsets).<br>
<br>
</div>Cool, thanks!<br>
<div class="im"><br>
> I've filed bug #683<br>
<br>
</div>Thanks! I just sent a patch for this, let me know if it resolves it for<br>
you. It's actually silly internal logic and not related to config<br>
objects. Nice catch :)<br>
<div class="HOEnZb"><div class="h5"><br>
--<br>
Dan Smith<br>
<a href="http://www.danplanet.com" target="_blank">www.danplanet.com</a><br>
KK7DS<br>
</div></div><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><br clear="all"><div><br></div>-- <br>
<div><span style="color:rgb(102,102,102)">Sean Burford <<a href="mailto:sburford@google.com" target="_blank">sburford@google.com</a>></span></div>
</div>