Skip to content
GitLab
Menu
Projects
Groups
Snippets
Help
Help
Support
Community forum
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in
Toggle navigation
Menu
Open sidebar
PIM
KAlarm
Commits
eba9ae09
Commit
eba9ae09
authored
Jan 11, 2021
by
David Jarvie
Browse files
Default to using alarm names
parent
b00944cb
Pipeline
#47266
passed with stage
in 13 minutes and 7 seconds
Changes
3
Pipelines
1
Hide whitespace changes
Inline
Side-by-side
CMakeLists.txt
View file @
eba9ae09
...
...
@@ -2,7 +2,7 @@ cmake_minimum_required(VERSION 3.5)
set
(
PIM_VERSION
"5.16.2"
)
set
(
PIM_VERSION
${
PIM_VERSION
}
)
set
(
RELEASE_SERVICE_VERSION
"20.12.2"
)
set
(
KALARM_VERSION
"3.1.
1
"
)
set
(
KALARM_VERSION
"3.1.
2
"
)
project
(
kalarm VERSION
${
KALARM_VERSION
}
)
...
...
Changelog
View file @
eba9ae09
KAlarm Change Log
=== Version 3.1.2 (KDE Applications 20.12.2) --- 11 January 2021 ===
* Default to using alarm names.
=== Version 3.1.1 (KDE Applications 20.12.1) --- 18 December 2020 ===
* Ensure that build uses the file resources option.
* When removing duplicate Akonadi resources, in priority keep enabled/standard ones.
...
...
src/data/kalarmconfig.kcfg
View file @
eba9ae09
...
...
@@ -94,7 +94,7 @@ SPDX-License-Identifier: GPL-2.0-or-later
<entry
name=
"UseAlarmName"
type=
"Bool"
>
<label
context=
"@label"
>
Enable alarm names
</label>
<whatsthis
context=
"@info:whatsthis"
>
Choose whether to be able to give alarms a name. This is a convenience to help you to identify alarms.
</whatsthis>
<default>
fals
e
</default>
<default>
tru
e
</default>
<emit
signal=
"useAlarmNameChanged"
/>
</entry>
<entry
name=
"MessageFont"
type=
"Font"
>
...
...
Write
Preview
Supports
Markdown
0%
Try again
or
attach a new file
.
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment