Add a new KAlarm calendar file resource. Its config file is created correctly, but it is not seen by KAlarm until Akonadi is restarted. Version 2.12.2, KDE Applications 19.04.1, on Neon.
When the KAlarm resource configuration dialog was used to create a new single file calendar resource, the collection was configured incorrectly in the Akonadi database. This is now fixed in kdepim-runtime, Applications/19.04 branch, by commit 5453e43e9af511b25e2f9bee93b737fe4dd04653. This will be released in KDE Applications 19.04.3. This removes the need to restart Akonadi in order to see new KAlarm calendar file resources in KAlarm. However, a KAlarm restart is now required instead.
A further fix to the handling of the resource configuration dialog has been applied to kalarm, Applications/19.04 branch, by commit 4db8a94f7e94555607312d35e023f8c962708231. This will be released in KDE Applications 19.04.3. A KAlarm restart is still required in order to see new KAlarm calendar file resources in KAlarm.
When a new resource was created, it was unusable until after an Akonadi restart (it was reported as having an invalid format). If a new resource used an existing calendar file, the file contents were not read. If a new resource used a new calendar file, the file was not created. A read and write of the calendar file are now performed, and a new resource is immediately usable. Fixed in kdepim-runtime, Applications/19.04 branch, by commit 6b47cbcbb8f57dd6c2b9b3a9fe56c95ca7f77fd8. This will be released in KDE Applications 19.04.3. A new resource still requires the user to manually enable it before it can be used. This needs to be fixed.
The Akonadi::EntityTreeModel class doesn't notify changes to the KAlarmAttribute collection attribute after it has been added by KAlarm. This meant resulted in the enabled status of a newly created calendar not being shown correctly, until KAlarm was restarted. A workaround has been implemented to fix the enabled status. Fixed in kalarm, Applications/19.04 branch, by commit bb465268cdddd5086c8d365c1bcd5250ec4b596e. This will be released in KDE Applications 19.04.3 (KAlarm version 2.12.4).