Martchus

I have no idea why the icon rendering doesn't work in this case. I tried to play around with the rendering code but it looks like it might be a...

The relevant code on my side is actually this line in `qtforkawesome`: https://github.com/Martchus/qtforkawesome/compare/v0.1.0...v0.2.1#diff-bbdda2a0a28454037de0dc03c0077fd4b526a8b0027652e04e8d3e88c70ad8ecR151 But it hasn't changed for quite a while in it is merely using `QIcon::pixmap()`.

Looks like this is still broken on Qt 6.7.3. The icons look good on a plain Qt Quick application when using Qt ForkAwesome in the same way (when using `Data::setForkAwesomeThemeOverrides()`)....

I guess that would make notifications much more useful, indeed. Let's see when I'll find the time to implement something like that. So far I refrained from folder-specific settings because...

This is not supported. You probably wanted to open a feature request and not a bug. An issue requesting this feature has already been created but I can't find it...

I at least found the relevant Qt upstream feature request again: https://bugreports.qt.io/browse/QTBUG-102855 So this is supposed to work as of Qt 6.8.0. Judging by https://codereview.qt-project.org/c/qt/qtbase/+/550202/9 you need to use `unix+http`...

Maybe you want to regenerate your API key now :-) > Syncthing itself doesn't seem to be starting - See screenshot Where do you see that Syncthing itself isn't starting...

So I take that as a "it work if configured correctly". If that's correct then I would close this issue and perhaps extend the README with your findings.

Ah, so one cannot just spend the path for the specific route. So the key seems to be specifying the URL as usual and passing the special `unix+http` URL only...

I'm a bit sick but maybe this is simple enough to come up with an implementation quickly. I just need to introduce a new setting and use it when making...