https://bugs.kde.org/show_bug.cgi?id=417108
David Jarvie <djar...@kde.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |FIXED
Status|REOPENED |RESOLVED
Version Fixed In|20.04.2 |20.12.3
Latest Commit|c907ac805bfc605e29a79455d78 |5ca740ebcbd8299c3c537207073
|aad0dde4acf71 |85b49dad8e669
--- Comment #23 from David Jarvie <djar...@kde.org> ---
If there is only one active alarm calendar, creating an alarm from the command
line will now work even if the calendar is not already marked as the default
calendar. This fits what happens if you create an alarm interactively. This is
implemented by commit 05bf384f67c59b6375726ddf53ca4298c095e376 in release/20.12
branch, and will be in KAlarm version 3.1.3 in KDE release 20.12.3.
If KAlarm was not already running, and a command line command to create a new
alarm fails, KAlarm will exit. This is implemented by commit
5ca740ebcbd8299c3c53720707385b49dad8e669 in release/20.12 branch, and will be
in KAlarm version 3.1.3 in KDE release 20.12.3.
If the failure to create a new alarm from the command line is due to no default
calendar being defined, an error message will be output on the terminal. This
is implemented by commit fc678bcaaddad744efe3ccb83916427d92b97713 in master,
and will be in KAlarm version 3.2 in KDE release 21.04.
If an alarm is created from the command line when KAlarm was not previously
running, KAlarm will not quit after creating the alarm. This is to ensure that
an alarm created from the command line will actually trigger when it is due.
--
You are receiving this mail because:
You are watching all bug changes.
