This makes the code more explicit about avoiding triggering the setup
detection twice. Maybe it fixes
https://github.com/Martchus/syncthingtray/issues/174 but likely it does not
change the behavior (in general).
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.
Otherwise it is not really possible to go back to the start page. Besides,
triggering the setup detection again explicitly might make it more obvious
what's going on.
The currently running instance might be from the launcher itself as the
wizard might have been started after configuring the launcher manually. So
let's just not mess with the launcher settings at all in this case.
* Add page to apply settings
* Add page to show final result
* Fix updating systemd checkbox (`isVisible()` did not work because when
the function is running the whole page is not visible)
* Enable systemd integration by default if either the user service or the
system service are running
* Fix typo
Otherwise the wizard would immediately start when accessed via settings
which is not very nice. Of course the instructions in the welcome page need
to be slightly adjusted.
* Provide icons for command link buttons because it looks rather bad when
some of them are missing in the user's icon theme and are therefore not
displayed at all
* Add icons to lists for bundling icons