(13-10-2026, 05:37 PM)EA3GCV Wrote: 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

(13-10-2026, 05:58 PM)EI4KF Wrote:

(13-10-2026, 05:37 PM)EA3GCV Wrote: 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

Hello Jordi

I'm with you, delete the v5 from those files. If you can find the way to do the migration. It has to be the best way, as you already know, not just for this upgrade but also so that in the future there is no version link in files to hold back development. It is a one time hurdle to overcome but it will be worth it. You can do it!! 

I'm all for V7 - I shall be promoting where I can, especially Flex Radio Forum. You could do with other marketing helpers, any Swisslog user that you know that uses a radio brand with a user or community forum in which they can post the update news. Like the SunSDR forum for example. 

Anyway I'm about to test the latest beta. Any issues, I'll let you know - I hope not but then that's what Beta versions are for. 

Erik.

(13-10-2026, 07:14 PM)EA3GCV Wrote: Hi Erik,

Thank you for the report. I will try to reproduce this scenario to find out the issue. So the issues only comes when there a high number of EU stations on a certain band?

73

(13-10-2026, 07:35 PM)EI4KF Wrote:

(13-10-2026, 07:14 PM)EA3GCV Wrote: Hi Erik,

Thank you for the report. I will try to reproduce this scenario to find out the issue. So the issues only comes when there a high number of EU stations on a certain band?

73

Hello Jordi

I think so. I changed bands on CW mode, checked for EU signals on each band. There were some and they were filtered out. I went to 30m CW where there was a large pile up of EU for the H49A operation. This is in my picture. None were filtered out as you can see. But then I activated the Criteria window, as you see it in the picture with EU filtered out. I clicked OK and all the EU Spots disappeared - they became filtered out. As new EU signals were Spotted by Clusters, they were filtered out. By the way, later I changed bands and then returned to 30m and EU remained filtered out. So I closed Swisslog, re-launched it on 30m and all the EUs were again not filtered.  So maybe, I am guessing, it is something to do with the massive rush of stations to the band map window when a very busy band is selected.

Erik.

(Yesterday, 12:05 AM)EA3GCV Wrote: Hello Wrik,

Sorry for the delay but I'm very busy these days. I will review all this carefully to try to find out what may happen. As you can see all is very complex in the Swisslog code and any improvement always rise unexpected results. A bit disappointing after all the hard work,  but I hope to succeed..

73

(Yesterday, 04:10 PM)EA3GCV Wrote: Hello Erik,

I have just uploaded a new beta today 15th October fixing this. Finally it's been easier than expected! I didn't include the routine to read the filter settings when Swisslog starts (as it is in the Criterias) and that was causing this issue. I hope now it's definitely solved (I tested here before releasing the beta and works well).

73