This release 

- when controlling an Icom transceiver like the new IC-7300 that supports A/B VFO selection and reports VFO B, correctly updates the "other" VFO display when performing an AxB or XFC function (tnx to Tim NZ8J)

- when the frequency approaches a band edge as defined by the current sub-band definition file, moves the Bandspread window's frequency indicator rather than its frequency scale (tnx to Joe W4TV)

- increases the maxiumn number of sub-bands per band from 2 to 8  (tnx to Joe W4TV)

- eliminates hardcoded sub-band definitions for the 1.25m, 33cm, and 23cm bands, and adds entries for these sub-bands to DefaultBandSegments.txt:

1.25M, 222.000, 225.000, 0
33CM, 902.000,928.000, 0
23CM, 1240.000,1300.000, 0

- updates the Configuration.htm documentation file


Notes:

1. As is described in

<http://www.dxlabsuite.com/commander/Help/Configuration.htm#Defining sub-bands>

Commander's sub-band definition file designates sub-bands on which operation is permitted; when the primary transceiver's active VFO is tuned to a frequency not within a sub-band, that VFO's frequency and the Bandspread window's current frequency marker are displayed with the "out-of-band" color. Commander obtains sub-band definitions from the file BandSegments.txt; if this file does not exist, Commander obtains sub-band definitions from the file DefaultBandSegments.txt, which is included in each Commander release.

Previous versions of Commander included hardcoded sub-band definitions for the 1.25M, 33CM, and 23CM bands, ignoring any definitions for these bands found in BandSegments.txt or DefaultBandSegments.txt. This version of Commander eliminates those hard-coded definitions, and adds sub-band definitions  for 1.25M, 33CM, and 23CM bands to the DefaultBandSegments.txt. If you’ve defined your own BandSegments.txt file and use these bands, you must add the appropriate sub-band definitions to BandSegments.txt.

2. Update your firewall and anti-malware applications to consider this new version of Commander to be "safe" 

3. If this upgrade doesn't work correctly, see the "After an Upgrade" section of <http://www.dxlabsuite.com/dxlabwiki/ApplicationStoppedWorking>

4. After upgrading, to revert to the previous version of Commander, see <http://www.dxlabsuite.com/dxlabwiki/RevertApplicationVersion>


Commander 12.1.8 is available via the DXLab Launcher and via 

<http://www.dxlabsuite.com/download.htm>

     73,

          Dave, AA6YQ