This reverts commit 8cac56c246 and extends
the related comment as the new Windows 11 style actually supports custom
palettes and then wizard's aero style breaks in the same way as with
Fusion.
This test would keep the autostart disabled but override an existing
autostart entry (see https://github.com/Martchus/syncthingtray/issues/221).
With this change it will no longer override an existing entry. Reading and
writing the autostart entry is now mocked and properly checked.
It looks like Qt Svg supports masking as of 6.7 which revealed a bug in the
code for making Syncthing icons. The mask for the emblem area was also
accidentally applied in case no emblem is shown. This change adds the mask
only when an emblem is shown.
* Use colors from palette; with this the custom scrollbars should always
be a plus (and not only when the Breeze style is used)
* React to palette changes at runtime
* The code is disabled under many platforms where the Breeze style is
unlikely to be used anyways.
* The code is disabled if Qt is older than 6.1 because only then the name
of the current style can be determined.
* Simplify `TopLevelItem` to what is actually needed to make it easier to
understand
* Use `onEntered` instead of `onContainsMouseChanged` which apparently
works better (with `onContainsMouseChanged` the selection/highlighting
did not always work reliably)
Porting to Plasma 6 seems more difficult than anticipated so let's be clear
that only Plasma 5 is supported. Reference the porting guide for future
reference; maybe it makes sense to look into this again in the future.
The alpha defines the macros
```
#define PLASMA_VERSION_MAJOR 5
#define PLASMA_VERSION_MINOR 27
#define PLASMA_VERSION_PATCH 80
```
so the current version checks (which were created based on the macros from
a development build) are not working. I have no clue how these numbers are
crafted so it is supposedly the easiest to just check for Qt 6 as Qt itself
uses a sane versioning system.
As of version 6 Plasma does not seem to pull-in its own dependencies
automatically. This might be a bug. For now, let's just workaround it by
pulling-in the dependencies manually.
This fixes the error `The link interface of target "KF6::Plasma" contains:
KF6::ConfigCore but the target was not found.`.