* Add template for other issues so it doesn't look like bug reports and
feature requests are the only options
* Encourage users to read the README before filing issues
* Clarify that issues about specific operating systems and tooling are out
of scope
The first test really needs to wait until Syncthing is listening. It is not
strictly required for testing the wizard's behavior. However, the next test
for connecting to a running Syncthing instance relies on Syncthing being
ready and listening.
Apparently 1.66 is broken as it does not invoke the `on_exit` handler when
the process finishes. When switching from 1.66 to 1.75 on Leap 15.4 the
problem is not reproducible. Maybe this was already fixed in an earlier
version than 1.75 but 1.75 was the next version available on Leap 15.4 to
test with.
* Show required URL format as placeholder text with an example
* Add explanation where to find API key as placeholder text
* Add explanation to authentication checkbox
* Move API key above authentication as it is more important
* See https://github.com/Martchus/syncthingtray/issues/172
In this case the connection from the setup detection is not the correct
one. The connection used to apply the settings should generally be used for
querying the QR-code.
When the launcher has already been setup and the wizard is opened and the
currently running Syncthing instance is selected, then the wizard said the
autostart option had no effect on Syncthing itself. However, that's not
correct when the currently running Syncthing instance has already been
started via the internal launcher. This change adds a special note for this
case which is actually correct.
* Avoid adding compile definition project-wide
* Use `SYNCTHINGWIDGETS_`-prefix for definition as it is done in other
places as well
* Use `set(… CACHE …)` for this non-boolean cache variable