https://bugs.kde.org/show_bug.cgi?id=481024

--- Comment #8 from Flossy Cat <flossy-...@online.de> ---
(In reply to David Faure from comment #4)
> I was told this was because freedesktop.org notifications don't support
> custom widgets, only a few action buttons, for interoperability with other
> desktop environments. 

I know – but this only demonstrates the choice to move to "freedesktop.org
notifications" as sole solution was ill-advided.

> I agree however this is really suboptimal, especially when not caring for 
> other desktop environments.

"really suboptimal" is runner-up for the euphemism of the week …

IMHO it is a fundamental lack of respect and rude to long-term KDE users to
fundamentally break existing functionality (and their workflows) without proper
announcement and transition provisions.

The fatal decision happened around 2 years ago, complaints exist since more
than 18 month – without solution.
I was confronted with this breaking changes when non-suspecting upgrading my
distribution – and the heart-ripping decision to give up a quarter of a century
KDE PIM usage, if I do not find a working workaround within 2–3 weeks. (And
that is not the first incident of this time – but so far definitely the worst
and potentially final one.)

IMHO the proper way would have been to keep the old behavior as an option and
wait for the reaction for at least 2 years before cutting of the old
functionality.

> As for "workarounds", you can find the code in
> akonadi-calendar/reminder-daemon/alarmnotification.cpp line 135 and add more
> buttons like "remind tomorrow".

The number of buttons is limited and cannot provide for my variable needs, lest
the needs of the numerous others having raised similar complaints. This is *not
a viable workaround*.

Are there any D-Bus-events I could hook on?

> Maybe we should implement an alternative notification solution in kalendarac
> that looks more like the old korgac dialog (minus its bugs...).

Definitely. And very soon. 
Actually you should never have removed the original functionality without a
substitute or a transition strategy as lined out above.

-- 
You are receiving this mail because:
You are the assignee for the bug.

Reply via email to