possibly fixed in https://invent.kde.org/frameworks/kdav/-/commit/bf6628ff1da1661a6485a2199d2222611e1b2ae5

related bug report: https://bugs.kde.org/show_bug.cgi?id=441575 konversation should separate state config from settings config

I do not have commit access. Could you please commit this for me? I think it should also go to 5.12 beside the master branch.

IMO, aligned text makes it much more readable at a quick glance. Thus, just from the pure appearance POV I would prefer the current solution.

minor formatting

minor formatting

minor formatting

update documentation

I was thinking if I should also add "th" for a more complete table tag set, but decided to keep it minimal.

5.7.3 versions are currently missing in the bug tracker

In D7464#138460, @dhaumann wrote:

@tillschafer Given you are active for more than a year, you should consider getting an account.

increase version

I do not have the necessary permissions to land this commit, can you please push this for me?

hmm, another small thing: the timeout of the message is about 15 seconds, which is quite long. This is especially long since you just need a short feedback of an action you are actively doing. I.e. in comparison of a message that pops up asynchronously from your workflow you do not have to move your focus from you current task to the notification.

just a short feedback: tested the patches together with D2954 and everything works as expected

another minor issue: the notification symbol/icon is blurred and the old one from KDE 4 times.

i have applied that patch atop of plasma 5.8.0 and see the following problem: When using the shortcut multiple times, the messages get grouped, i.e. shown in a single popup. This causes the most relevant text to be hidden and you need to scroll down to actually see it (see attached screenshot for an example):

it is resolved in the meanwhile (see https://bugs.kde.org/show_bug.cgi?id=335654#c7)

I found the same request (missing versions) in the regular bug-tracker which lists the versions in more detail: https://bugs.kde.org/show_bug.cgi?id=335654#c7

• 5.1 aligns with Applications 15.12
• 5.1.x with 15.12.x
• 5.2.x with 16.04.x
• and so on

In D1479#43768, @broulik wrote:

Thanks for your feedback

It is possible to scroll one letter to the right, although there is a automatic line break.

I suppose that's the are the scroll bar occupies, I'll have a look.

what about this issue? It is not fixed yet.

i have tested this form a user perspective on fresh tags and it works without any problems so far. categories keep their color.

tested this changes in combination with https://phabricator.kde.org/D2423 on 16.07.90 and it works like a charm.
-> creation/modification of an event on one client with a new tag name, synchronized them over the DAV resource, look at new/changed event on another client. New tags are correctly created.

tested this changes in combination with https://phabricator.kde.org/D2433 on 16.07.90 and it works like a charm.
-> creation of new tags
-> visualizing existing tag assignments
-> creation/modification of an event on one client, synchronized them over the DAV resource, look at new/changed event on another client.

There are a few glitches left.

In D1141#21689, @elvisangelaccio wrote:

In D1141#21687, @tillschafer wrote:

isn't this proposal here quite similar to this one: https://phabricator.kde.org/T1769 ?

This is the implementation of that proposal :)

https://phabricator.kde.org/D1141 seems to be related

isn't this proposal here quite similar to this one: https://phabricator.kde.org/T1769 ?

In T1769#21689, @tillschafer wrote:

A second thought: Are there blocking actions shown in the progress bar? In this case the main window should also indicate that something is done and in the best case give the possibility to cancel the blocking action.

You mean actions that block the UI? There are, but they also can be stopped only from the progress bar in the system tray's notification (this is similar to how Dolphin hanldes KJobs, btw).

Yes, I thought, that is might be a bit cumbersome to find the right background job that is associated with the gui blocker if one has more than a single job running. E.g. if i pressed unpack and i got aware that i have chosen the wrong destination folder i need to find the right job in the tray instead of just hitting cancel in the area where i do my actual work.
However, consistency across the application is also beneficial.

A second thought: Are there blocking actions shown in the progress bar? In this case the main window should also indicate that something is done and in the best case give the possibility to cancel the blocking action.

Is it possible to detect if the system tray progress bar is shown? In this case, I propose to use the status bar only as a fallback for trayless systems (+ showing it only on demand).