• NEW: Band Map - Advanced filtering system:
      - Selection criteria — DXCC, Continent and Zone filters — The mode selection dialog now includes three additional filter: DXCC, Continent and Zone. Multiple values are supported in all three checkbox fields. Examples: EA, G, F for DXCC; EU, NA for Continent; 14, 33 for Zone. These filters allow precise control over which spots appear in the window based on the geographic origin of the DX station.
  
• NEW: French Regions: Swisslog will automatically fill out the French Region field in all QSO with French stations (DXCC = F) where user has set the DDFM number (French Departament)
  
• NEW: UDP Realtime saving and receiving UDP/TCP data in ADIF format: added State / Cnty ADIF fields (REGION, SUB-REGION respectively). When saving QSOs with DL stations the UDP packet will include the field DARC_DOK if the DOK field is filled out.
  
• NEW: Support for JTTY: added new mode and adapted ADIF import/export function to fulfill the new requirements in forthcoming ADIF specs 3.1.8
  
• NEW: Support for PAC, PAC2, PAC3 and PAC4: Renamed PACTOR mode to PAC to fulfill ADIF specs. Added new modes PAC2, PAC3 and PAC4
  
• Corrected: QSO Entry > Station tab: Notes field was displayed empty when adding a new QSO with a previously worked station having notes in the C_NOTE field.
  
• Corrected: QSO Entry > Station tab: Note field Unicode characters were displayed as ???.
  
• Corrected: Band Maps: double clicking on a spot, if one of the actions was Log QSO and the spot contained award info such as WFF, SOTA, DME, etc. these fields were not set in the QSO Entry window.
  
• Corrected: Dx Alerts: position and size were not restored after closing Swisslog.
  
• Corrected: Telnet server window: now accented latin characters are displayed properly
  
• Corrected: Routine to process Pendient Log QSO Requests: often one or some QSO were lost during the process of the queue of Pending Log QSO requests. Now the routine has been improved and it checks if the QSO has been really saved before deleting it from the queue. In case it's not saved the routine will process next queued QSO leaving this pending QSO in the queue to be processed later.
  
• Corrected: DEE info table: DME where not imported properly resulting with no leading zero in DME. Example: instead of 01001 was imported as 1001.
  
• Optimized: Transceiver control for TCI and Flex Radio: reduced traffic drastically improving overall performance
  
• Corrected: Logbook view: Manual tab: when selecting a MyQTH the following error message appears: Parameter L_MyQTHID has no default value.
  
• Corrected: Import ADIF QSO: selecting option "QSL action based on QSL Received/sent" fields didn't work and a blank QSL Action was set despite user assigned a value in the QSL-Action field.
  
• Corrected: QSO entry: QTH Locator was not set when reading from Callbook databases under very rare scenarios.
  
• Improved: Transceiver control: improved performance and stability reducing port traffic and internal messages.
  
• Corrected: Band Maps: solved reported filtering issues. If user checked all modes, not all were checked after restarting Swisslog.
  

(12-10-2026, 12:33 PM)EA3GCV Wrote: Hello Erik,

HAHAHA I knew you will be impatient! I will try to release a Beta with the new DX Message window before Christmas. Stay tuned!

Regarding the version numbering, the "problem" is that latest v5 Walter released was 5.8. When I started to develop Swisslog I released 5.9. then I followed with 5.91, 5.92 until I quickly arrived to 5.99! I could not release 5.1 because this version already existed! That's why I decided to continue with 5.100, 5.101 and so on. This way I have many numbers to get to 5.999! :-p

I could do a jump to 5.200 but I think version numbering is not really important. Users should know than in Swisslog, a "small" version numbering change (such as 5.118 to 5.119) doesn't mean there are minor changes. Every new version may contain dozens of important improvements even if version numbering may think users the contrary. What is really important is that users always use latest version regardless version numbering. 

73

(12-10-2026, 02:45 PM)EI4KF Wrote:

(12-10-2026, 12:33 PM)EA3GCV Wrote: Hello Erik,

HAHAHA I knew you will be impatient! I will try to release a Beta with the new DX Message window before Christmas. Stay tuned!

Regarding the version numbering, the "problem" is that latest v5 Walter released was 5.8. When I started to develop Swisslog I released 5.9. then I followed with 5.91, 5.92 until I quickly arrived to 5.99! I could not release 5.1 because this version already existed! That's why I decided to continue with 5.100, 5.101 and so on. This way I have many numbers to get to 5.999! :-p

I could do a jump to 5.200 but I think version numbering is not really important. Users should know than in Swisslog, a "small" version numbering change (such as 5.118 to 5.119) doesn't mean there are minor changes. Every new version may contain dozens of important improvements even if version numbering may think users the contrary. What is really important is that users always use latest version regardless version numbering. 

73

Ok on a possible Beta. I'm tuned hi.

Yes I understand about version numbering though I had forgotten about Walter's 5.8 and the natural progression to 5.9, 5.10 etc. It is just that a seismic update gets more notice if the marketing promotes it. So, of course carry on and no problem at all. I'd release it as Version 7 hi.  I think Swisslog is way ahead of other logbook programs and I wish there were more users and it gained many new ones. Not just because I am sure new adoptees would benefit but also because you do so much work on SWL. However, as we know: old English saying... you can lead a horse to water but you cannot make it drink.