[DXLog.net - Support] Version 2.1.8 in testing phase

[9A5K]

Hi all.

DXLog.net version 2.1.8 is now in testing phase.
Everyone who has access to devtest folder can try it now.
There are some new things implemented: bandmap list sorting, SO2V mode etc.
DXCluster received spots data are now optimized in the code, and it should
work more reliable with less resources needed.

I hope that new version will be available to public around during this week.
For sure, SO2V mode brings quite a lot of new things in the code and should
be tested little bit more carefully.
Still trying to add UPDATE DATABASE command, so you will be possible to
update databases with callsign and received data
directly from your own log. If there will be enough time, this will be
added to 2.1.8, otherwise will be implemented in v2.1.9.

Here is the c/p from release notes what's new and fixed:

Ver 2.1.8
------------------------
- New shortcuts/menu options available:
  CTRL+ALT+UP   - grabs first valid upper spot and sends a frequency to
inactive VFO.
  CTRL+ALT+DOWN - grabs first valid lower spot and sends a frequency to
inactive VFO.
  Menu options are:
  Operating->Bandmap->Grab first valid upper spot to 2nd VFO
  Operating->Bandmap->Grab first valid lower spot to 2nd VFO
  Starting point for frequency is inactive VFO frequency. In case that
inactive VFO is on different band then active one,
  start point will be the frequency from active VFO, so band of inactive
VFO will be changed to same as active one. (TNX I4UFH)
- RDA Contest - ADIF export changed to CNTY/STATE. (TNX E73Y)
- RDA Contest - added calculation for Russian "/P" stations. (TNX UA6AA)
- LZ HF Field - new window available - worked callsigns. Shows which
callsigns are worked during the contest with information
  about when new qso with same station will be available. (TNX 4O3A)
- Band changes counters added for multi/single and multi/two categories in
CQ WW RTTY. (TNX EI3JE)
- New option added: Tools->Data entry->Prefill values
  Callsign value - when new qso row is initialized, it is automatically
prefilled with desired value. (TNX 4O3A)
- OTRSP device - AUX pins wasn't switched correctly. Fixed. (TNX K6ND, N1RR)
- NA Sprint - own multiplier wasn't counted. Fixed. (TNX W9PA)
- All Asian - multiplier window was broken when some special prefix was
worked (for example HS50). Fixed. (TNX 9A2NO)
- WAE DX Contest - added some optimization in QTC receive window. QTC's
also can be edited after save.
- Azimuth info shown in Check multiplier window was wrong when gridsquare
was filled at config screen.
- Bugfix: cat command for SSB mode change was based on current band, not
new one, when band was changing with frequency typing in callsign field.
  Because of this, when band was changed for example from 40 to 20m  mode
was set to LSB (current band = 40m) instead of USB (new band = 20m). Fixed.
(TNX W9PA)
- Bugfix: worked DXCC window font size wasn't correctly restored when log
is opened. Fixed. (TNX W9PA)
- New option available in Radio config screen: Use CI-V (don't poll).
  This option will enable usage of CI-V transceive mode for ICOM radios,
instead of standard radio cat polling.
  In previous versions enabled CI-V transceive mode on some radios caused
CAT communication error which disconnects the radio until port is opened
again.
- New multipliers added for contest KT KUP Srbije. (TNX YT3W)
- Bugfix: config file for KT KUP Srbije missed Cabrillo operator category
for NON-YU category. Fixed.
- SAC Contest: added serial number definition for all categories.
- Single OP 2 VFO mode (SO2V) is now enabled.
- Rate window - qso and multiplier worth informations added.
- DXCluster data manipulation code is completely rewritten to optimize
performance.
- Bandmap list sorting options added.
- New option available: Options->Interface specific options->Prevent TX if
another radio on same band.
  If checked, it will prevent TX if we found another radio (Radio1 vs
Radio2 in SO2R mode, or any networked radio if network is enabled) is on
same band.
  Currently, in network mode, we are comparing our TX radio band with BAND
field in network list.
  Please note that in case of network failure, we can't determine another
radio band, so this should be just temporary solution and some hardware
solution
  will be much safer for such scenarios. (TNX K6ND, N1RR)

73,
Chris - 9A5K