There are statically linked Windows binaries attached on the latest GitHub release: https://github.com/Martchus/syncthingtray/releases
If you looked at my website for dynamically linked binaries: Yes, those are outdated. Since the statically linked ones should be sufficient I currently don’t put any effort into it.
Ah, you want to build it yourself? Have a look at PKGBUILDs/syncthingtray at master · Martchus/PKGBUILDs · GitHub. Those PKGBUILD files are for building the Windows version under Arch Linux, but they show required dependencies and commands to be executed quite clear. So you can use that information to build under other platforms as well. Of course there are also general build instructions.
New release 0.9.1 is available.
I don’t create a post for every release so the list of changes since the last post is quite long: https://github.com/Martchus/syncthingtray/compare/v0.8.0...v0.9.1
I mainly did some small adjustments since the tray basically covers my own use-cases. The most notable change is the use of font awesome in accordance with the official web UI.
I’ve also been able to build and test under s390x. I’ve created a SLES repo on OBS which covers also Syncthing itself.
The screenshots of the initial post are now pretty outdated. There’s no way to amend the initial post, right? It would be nice to add at least a link to the more frequently updated screenshot section on GitHub: https://github.com/Martchus/syncthingtray#screenshots
The next release will feature customizable icons. This way the icon can be adjusted to integrate much better with the rest of the system tray. Here’s a screenshot how it might look like under Tumbleweed with Plasma 5:
Since a Mac version was requested some time ago: A user could build is successfully and it seems to work basically. There are still some problems but the progress is tracked on GitHub. Of course this does not mean I will be able to provide binaries myself but it is already a step further.
Thanks to yan12125 the Mac version of the current development branch can now be installed via MacPorts.
New release v0.10.0 is available.
I already mentioned some of the new features. Besides, also some bug fixing and minor improvements have been done. Here’s a full list of changes: https://github.com/Martchus/syncthingtray/compare/v0.9.1...v0.10.0
New release v0.10.2 is available.
This release contains only minor fixes and improvements compared to v0.10.0: https://github.com/Martchus/syncthingtray/compare/v0.10.0...v0.10.2
I’d like to test for Windows. Should I remove SyncTrayzor first or can they run concurrently?
I don’t know the SyncTrayzor side but Syncthing Tray will by default not even start Syncthing automatically for you. So you can easily use it with a Syncthing instance started independently, eg. via SyncTrayzor. If you decide to keep using only Syncthing Tray you can configure its launcher to start Syncthing for you. Then you should ensure no other instance is running at the same time but I think the worst which can happen is an error when starting the 2nd instance.
Thanks! 
New release v0.10.3 is available.
It contains fixes for Qt 5.14 and Plasma 5.17 and updates “libsyncthing” to v1.3.1: https://github.com/Martchus/syncthingtray/compare/v0.10.2...v0.10.3
Please add support for Debian.
Maybe you should ask people who create Debian packages. From the upstream side I see nothing which would prevent one from using it under Debian.
Hey, sorry if this is a dumb question, but is there functionality to connect to the primary ST instance when the tray application starts up?
It is not a dumb question because there is indeed room for improvement in this area.
So far the tray can connect automatically to the primary (or currently selected) Syncthing instance when it notices that the instance becomes available. However, it can only notice that the instance becomes available when it is started within the built-in launcher or when it is started via systemd and Syncthing Tray is configured to keep track of that systemd unit. Otherwise it will not be able to connect automatically.
It should be quite simple to add an auto-connect checkbox within the connection settings. I just haven’t done it because I usually use the built-in launcher or systemd.
I implemented an option to automatically connect regardless of the launcher or systemd status. It will be part of the next release.
New release v0.11.0 is available.
Compared to the last post here a lot of changes have piled up so I hope it feels more polished in overall: https://github.com/Martchus/syncthingtray/releases/tag/v0.11.0
New release v1.0.0 is available.
Again, there were mainly smaller changes: https://github.com/Martchus/syncthingtray/compare/v0.11.0...v1.0.0
I’d also like to note that there’s currently a discussion regarding the remote device status: https://github.com/Martchus/syncthingtray/issues/74
Maybe someone who knows Syncthing’s internals better than me can give me some advice how to proceed with that issue.
Please forgive me if this is something obvious, but is there a way to change the default path where syncthingtray.ini is stored?
There does not seem to be any built-in way (e.g. a command line switch) to do it. I have tried looking for some kind of an universal method for Qt to override the default config path, but my knowledge of it is limited, and I also have not managed to find anything useful online.
