Why don't you set up the preferred size for the dialogue, and allow the label to be multi-line?

Welcome back :)

so if something doesn't work, let me know ;-)

Updated to fix the issues.

What's the status of this patch?

The changes are pretty simple, but testing it would require a lot of work as it requires a full up-to-date KDE development system and I just don't have that option.

Hmmmmmm, api.kde.org certainly fooled me. Seems there are two classes with the same name in different packages!
Either way, one has a bug, not sure which was linked in.

Updated git and task comments to use XDG_DATA_HOME.

In D8469#160263, @cryptodude wrote:

Updated to use QStandardPaths

Updated to use QStandardPaths

I'm not sure the users will like what you did with encfs, but we can at least test the waters. :)

Ok, I see the confusion. The name of this pull request uses the word 'default' and that confused everyone.

I tested this version to do what I described.

In D8449#159406, @ivan wrote:

Having a default backend (IMO) has nothing to do with the UI.

In D8449#159337, @ngraham wrote:

I don't think choosing a random backend makes sense without at least some information provided to the user. How about adding a text view below the combobox showing a quick human-friendly summary of the purported advantage of each backend? like this: