Skip to content

Qt-DAB 6.30

Compare
Choose a tag to compare
@JvanKatwijk JvanKatwijk released this 27 Nov 13:19
· 73 commits to master since this release

Since 6.25 there are many changes, internally and visible, so it was time to freeze a release.
The most significant visible change is that what was called presets is now renamed "favorites" and is places in a
separare widget. Adding a servicename to the favorites is simplified: under normal settings, clicking with the right mouse button
on a service name in the ensemble window or in the scan list widget will add that name to the favorites.
Since this change was added to the 4 and 5 version as well, there are renamed.

Having the right library for the dabsticks seems to be an issue, that is why the (Windows) V6.30 is available in two versions, the regular 6.30 version uses the library that was developed for a.o the V4 dabsticks, the Qt-DAB V3 version has built-in support for the "old"
driver for "older" versions of the support library for rtlsdr based devices. Note that the 2 versions are identical, apart from the library that is linked in, their appearance is also identical. The Windows V4 and V5 versions are linked with the "old" support library.

For Linux x64 there are appimages, created on an Ubuntu 20 running VM.

The manual (attached) is updated to reflect the changes (well, at least hopefully).
A separate document exists - also attached - that gives some guidelines on building an executable. Note that it is
written on the afore mentioned U20 system, libraries may have other names on other distros. That document contains
a section on how to add a device to the list of supported devices.

Note that the Qt-DAB system supports interfaces to various devices, the approach is that by selecting a device, an attempt is
made to read the required functions from the device library, so the device libraries themselves are NOT included in the
precompiled Linux versions. They are included in the Windows installers though (that is why there are 2 versions)

While having "skin"s is nice, there was one drawback. On deselecting a service in the ensemble display, the font of the deselected service was made black. While for most of the skins the background is black, it meant that the servicename was essentially invisible. The default setting now is "white". In the ".ini" file you can set the default servicename color to whatever you want with "fontColor=XXX", where the XXX stands for a stringname of a color. Version 6.30 - both the W installer and the AppImage included - contains on the configuration and control widget a button for setting the color. Note that the versions 4 and 5 will use that color.

Just a minor update, not enough for a new version number
Latest update: issue in scheduling,.