Since the first version of 6.X was uploaded, a lot of changes were made. One of the - for me - more annoying things was the mess that was made of the "ini" file. So, one of the changes is that the structure of the ini file was (re)designed, and
made into clean paragraphs.
The drawback is that the new ini file is not compatible with the old one, therefore the ini file for the 6.8 version is named differently.
It means (a.o) that settings done for older versions - in particular the home position for using the TII decoding - has to be redone.
When starting the first time, a warning will appear to indicate that the home location is to be filled in.
A second visible change is that the software now records for each channel the service selected, and - on re-enetering the channel -
will (try to) restart the service.
As before, files generated by the software, i.e. slides if they are saved, the tii text file and the log file - if enabled - appear in the folder (or directory ffor Linux) "Qt-DAB-files", in the user's home directory.
The configuration and control idget has a button "path" when touched, allows setting a different path for that file
Minor addition: I found out that some young people had trouble figuring out which direction e.g. 330 degrees azimut was,
so I added a compass to the dxDisplay, showing the direction of the strongest signal, i.e. the one used in processing
12-11 small update, some settings in the new ini file were incorrectly handled
15-11 updates, some scanning functions did not work, skip (or scan)table handling modified and corrected
Qt is the framework with which Qt-DAB (note the name) is built. While for the past years Qt5 was used, nowadays it is all Qt6. Most of the differences are manaegable quite well, the sound handling in Qt6 differes considerably for that in Qt5.
So, for some time now, I am rewriting things required for Qt6.
A few problems occur
a. AppImages are to be developed with "older" libraries, that is why I am using Ubuntu 20 for generating AppImages, and in U20 there is no support for Qt6, so until I either have installed Qt6 (and Qwt 6.2) on U20 or U22 is "old enough" I'll generate AppImages on U20 with Qt5
b. While the rewritten sound handling works fine under Linux, there is a sound problem with Q6 sound output under Windows, I am working on it. Until that is solved it does not make sense to make installers for Qt-DAB built on Qt6 available, and the installers will be based on using Qt5
(The sourcetree is such that without problems Qt-DAB can be compiled with either Qt5 or Qt6)
Since, while working on the conversion from Qt5 to Qt6, I made some other changes as well, the current intermediate version is named 6.9, and it is still slightly experimental. However, I added an AppImage and a 64 bit Windows installer
While some details still have to be modified, the development of the version that can be compiled with Qt5 or with Qt6 reaches completion. Unfortunately, one of the - nasty - details is that the Windows versions when compiled using Qt6 still give problems 👍 they run perfectly, but the soundoutput with Qt_audio does not work yet.s), so windows versions are still compiled with Qt5.
Test versions - one for Linux and one for W64 - have been attached to this list (setup-dab64-qt5-6.9. exe as a windows installer and Qt_DAB-6.9-x86_64.AppImage as a Linux AppImage_