Yes, this is a good approach.

I suggest you create ONE new widget which contains a slider and a spinbox, and you pass the range it shall use.
Now it's very confusing.

other than ma comments, I'm ok with it.

I was talking about the code I changed, which uses QUrl, which can not parse the @SSL syntax.
I tried.

file://some.server:80/DavWWWRoot/pwa/some/path/to/a/document clearly works since it's standard URL syntax.
file://some.server@80/DavWWWRoot/pwa/some/path/to/a/document does not, since it's not a valid URL syntax.

ping

About SSL: I have no idea how an SSL url from a sharepoint server would look like, since it seems the setup we use does not use ssl.
The mentioned webdavsystem.com link just describes how it would look like as a win-UNC path, but since I receive urls in mail which are not in the unc syntax, I'm not sure if they will contain this @ssl token or not

Have you tested creating a new deployable Windows package?

ping

This is what I get (without my patch) when hitting "check for mails" in kmail:

I also reported this problem before at https://bugs.kde.org/show_bug.cgi?id=397131

I now committed the patch adapted to your latest suggestion just setting top/bottom margins of hbox to zero.
I don't want to change the separator though.
I think you need to close this issue now manually.

I don't have 5.11 RC right now to test, but the fix seems reasonable.

Can you explain a bit more in detail why you think this change is useful ?
What stylesheet are you using ? What is your exact setup ?
maybe show a screenshot of the problem you see with the old margins.

In D12019#243886, @knauss wrote:

But the whole createUniqueFileName is not supposed to generate unique names anyways, as it is used in a do loop in Maildir::addEntry. I think be better approach to add to mutex, to garantee
QFile::exists(key) || QFile::exists(finalKey) || QFile::exists(curKey) is valid. Maybe we should touch the file in tmp dir immediately. And than it is irrelevant if we use a not so good createUniqueFileName.

changed to milliSeconds.
Altough I'm not really sure if this is a good solution, since how can we know how fast computers will be in some years ?
And QUuid is there for exactly this reason - to generate a unique name.
Yes, the filenames are twice as long - altough: who cares ? Do you think it hurts somewhere ?

In the spectacle section, this part has a typo (buton) and is not really understandable:
"... and how displays a buton to open the Settings window..."

Don't know if that is automatically included somehow: There is a new application in kde utils: kbackup