FWIW I was just triaging a bug report in which users were complaining
about missing KAlarm notifications. After thinking about it a bit, I
think that it's appropriate for "alarm/timer finished" notifications to
be persistent and not time out; if you miss the notification that the
alarm or timer has finished, the entire point of setting it in the first
place is defeated.
On 9/19/20 8:42 AM, David Jarvie wrote:
On 18 September 2020 17:12:48 BST, David Edmundson <da...@davidedmundson.co.uk>
wrote:
On Fri, Sep 18, 2020 at 3:45 PM Kai Uwe Broulik
<k...@privat.broulik.de>
wrote:
Hi,
Is it possible for the application to change its own "show in
history"
setting, instead of the user going to System Settings to do this?
It is not.
Let's back up a bit, what's the end goal we're trying to achieve for
the
kalarm notifications that isn't fulfilled out of the box.
I'd considered providing a setting to choose between persistent notifications,
which wouldn't need to show in history, or for notifications to hide after
timeout, which would require them to show in history. If, as you say, the
application can't change the history setting, I won't provide the persistent
notification option (which in any case could be considered to duplicate the
existing functionality using notification windows).
--
David Jarvie
KAlarm author, KDE developer
