Beta released on 13th October 2026

[EA3GCV]

Dear users,

I have released a beta including the following improvements (latest changes highlighted in boldface):

• 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).
  
• 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 filtering issues. If user checked all modes, not all were checked after restarting Swisslog.
  

[EI4KF]

Hello Jordi,

Band Map filtering: excellent. Good job! Is this an indication that the filtering system will be available to the DX Message windows in the future?

By the way, are you aware of a minor issue: with EU filtered out, I do still get EU Spots show up on the Band Map. Some are soon deleted, within seconds in fact, but some take minutes to disappear. Better would be if the filtering could be more robust, if possible. Not a deal breaker - it is still better than no filtering.


   

When there are a lot of DX Spots that should be filtered out, the filtering does not work at all well

   



Erik

[JW6VDA]

Thanks Jordi. That was an extremely fast reaction to my report on the locator issue!
Next question: The ADIF v3 export query on my computer is quite old (from 2018). How can I obtain the most current version?
And lastly: Is there a way to filter out spots based on the spotter's country or continent? When chasing rare or difficult ones, the spots originating outside Europe aren't terribly informative for me here in Finland or even on my now rare trips to JW-land.

Again thanks for your good work and the extremely fast response!

73 de Tom OH6VDA

[EA3GCV]

Hello,

I have just released a new beta fixing the flltering issues.

Erik, yes I'm reworking the Dx Message window adding very interesting features! I'm working on it since many months ago. It will include the new selection criteria as the one I have included now on Band Maps, but also:

- Column sorting
- Quick column filters (allowing wildcards to filter on realtime)
- User will be able to invert spot order (most recent on top)
- Fully colour custimizable for titles, grid background, select spot and LoTW / eQSl indicators
- Improved stability and performance compared to the current one.

I have had to migrate to another grid component compatible with current code which offers more features. I'm under final testing, so stay tuned on this thread. My intention is to release version 5.119 officially on December (my usual Christmas gift!) and this a will be very special edition.

Tom for the moment I have not planned to implement spotter's country or continent filter on this release. This will be another improvement for next releases. Step by step.

73

[EI4KF]

Hello Jordi

I cannot wait for Christmas! You are doing great job. I think also you are busy with your job too, so it is not so easy. Is it not time to change the version numbering to 5.2 ?! It sounds like a massive step up from 5.1xx ....

[EA3GCV]

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

[JW6VDA]

Thanks for the new Beta!

One (small) issue I don't think I have mentioned before: when unchecking the LLOTA query and then closing Swisslog, the next time I open it, the LLOTA query is still checked. I wouild like it to remain unchecked. Even editing SwisslV5.ini is unhelpful, it is LLOTA is uncehcked when I start Swisslog, but next time it is back checked!

By the way, how can I obtain the updated ADIF export query?

 73 de Tom

[EI4KF]

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.

[EI4KF]

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.

In latest Beta, the filtering is not any better

   

[EA3GCV]

Hi Erik,

I have uploaded a new beta today which should solve definitely the band map filtering. I have been testing for a long time and it's working well here.

Regarding version numbering: I completely agree with you! I think it's time to change version number to version 7 which you know I created a brnad new logo since many years ago. But this big version number leads me to another "problem". As it is now, all important files are named as v5:

- SwisslV5.exe
- SwisslV5.mld
- SwisslV5.ini
- Swlog_v5.mdb

These 3 files MUST have the same file name. The EXE and MLD (language file) is easy to migrate to a new name SwisslV7.exe / SwisslV7.mld. But the configuration file need to be "migrated" otherwise user will have to reconfigure everything. The database name is not really important because the database version in displayed in the lower part of Swisslog as DB-Version.

I'm considering delete version number in the executable file and simply leave:

- Swisslog.exe
- Swisslog.mld
- Swisslog.ini
- Swlog.mdb (for new installations only). Current users may change the database name whenever they want.

Version number is displayed when executing Swisslog, no need to set version number in files. But I have to find out an easy way to migrate current configuration file to the new name during the installation with no user intervention. I have a very powerful installation software which offers many functions so I will study it. Probably I could find a renaming function. My preference is to delete v5 from these 3 files. What's your opinion? I will really like to release next version as 7.0.0. After 14 years improving version 5 it's time to a big version change and a new logo. Initial v5 has nothing to do with current version.

73