* Allow to pause all devices on metered network connections (devices will
be automatically resumed when network is no longer metered)
* Allow to stop Syncthing when it was started via the built-in launcher
on metered network connections (it will be automatically started again
when the network connection is no longer metered)
* See https://github.com/Martchus/syncthingtray/issues/231
* Avoid multiple definitions of `centerObj()`; this was very bad anyway
* Include `c++utilities/tests/testutils.h` upfront so the formatting
operators are included before CppUnit
Otherwise unity builds fail due to macro redefinitions. It doesn't really
matter what name is used in the web view files anyway (as it just changes
some environment variables used for debugging).
* Add include directory for testhelper library manually as using the
imported target was not possibly
* Fix visibility when using libsyncthing in syncthingwidgets
* Update changed global headers along the way
* Remove the old approach to specify actions as it is lacking the `Actions`
key and doesn't allow customizing the executable name
* Add actions for most important use cases
Syncthing added shell completion in v1.27.3-rc.1 (commit
78db3af8c5e8bd08a9773b0c4da233a52ed4cfe6). This change integrates
that shell completion with Syncthing Tray's long existing completion (which
only supports Bash so far).
* Unify code paths for compiling expected SSL errors so in any case the
expected errors are including the error types emitted by the Schannel
backend
* See https://github.com/Martchus/syncthingtray/issues/223
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.
