I haven't tested linking and execution yet; it would probably require to
use e.g. `mingw-w64-ucrt-x86_64-go` from MSYS2 (instead of
`mingw-w64-x86_64-go` where the stdlib clashes).
* Use CMake's command mode to set environment variables
* Only make use of `CMAKE_RANLIB` if set
* Avoid using the compiler/tools/flags from CMake via cgo when building
with MSVC as this doesn't work; this is problematic because stdlibs will
not necassarily match but this way we can at least compile the static
library
* Set content margins to take shadow effects into account
* Fix behavior when showing the QMenu not as `Qt::Popup`
* Prevent polishing as it would wrongly override our window flags
* Use the background color from the application's palette as the
background color from the QMenu itself is changed by the Windows 11
style
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.
Martchus