Hello, thanks for the patch, but in the Qt documentation I see the follwing note:
Note: Since Qt 5.14, range constructors are available for Qt's generic container classes and should be used in place of this method.
for both QList<T> QSet::toList() const and QList<T> QSet::values() const.
May be it's will be better to use range constructor, because values will probably be deprecated in future.
Hmm since Qt 5.14.... but I build QET packages for Debian Buster (Qt 5.11.x), Debian Sid (Qt 5.12.5) Ubuntu Bionic( Qt 5.9.).., etc... Only AppImage, macOS packages use Qt 5.14.2..maybe Flatpak and Snap.
For Qt 5.15 LTS it's still too early, I have a lot of problems with it.
/Qt/5.15.0/gcc_64/include/QtCore -Irelease -isystem /usr/include/libdrm -I. -I../../Qt/5.15.0/gcc_64/mkspecs/linux-g++ -o release/qetarguments.o ../sources/qetarguments.cpp
../sources/qetapp.cpp:44:25: fatal error: KAutoSaveFile: Aucun fichier ou dossier de ce type
Edit ; fixed
https://www.qt.io/blog/qt-online-instal … 3-released
argh ... I don't want to move to Qt shared libs for Windows is a pain for deploying under a cross-environment like MXE.