| Summary: | All created alarms disappear from the list after ringing | ||
|---|---|---|---|
| Product: | [Applications] kalarm | Reporter: | quanticcpu2100 |
| Component: | general | Assignee: | David Jarvie <djarvie> |
| Status: | RESOLVED NOT A BUG | ||
| Severity: | major | CC: | anditosan1000 |
| Priority: | NOR | ||
| Version First Reported In: | 3.8.1.1 | ||
| Target Milestone: | --- | ||
| Platform: | Fedora RPMs | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
quanticcpu2100
2024-07-09 08:04:12 UTC
What do you mean by "ringing"? (In reply to David Jarvie from comment #1) > What do you mean by "ringing"? The alarm sound. (In reply to David Jarvie from comment #1) > What do you mean by "ringing"? After all the alarms sounded. You can still see alarms which have previously triggered. They are "archived" alarms, and you can display them by menu action View -> Show Archived Alarms. To see them you also need to ensure that archived alarms are kept for as long as you need them. Go to Settings -> Configure KAlarm, and in the Storage tab you can choose whether to keep alarms after they expire, and for how long. Keep this option enabled by default to not confuse the end-user. (In reply to David Jarvie from comment #4) > You can still see alarms which have previously triggered. They are > "archived" alarms, and you can display them by menu action View -> Show > Archived Alarms. To see them you also need to ensure that archived alarms > are kept for as long as you need them. Go to Settings -> Configure KAlarm, > and in the Storage tab you can choose whether to keep alarms after they > expire, and for how long. Keep this option enabled by default to not confuse the end-user. If the alarm on Android cell phones doesn't hide the alarms previously configured by the user why does yours kalarm hide them? To make life difficult for the end user? You are the first user to complain about this in over 20 years, so I'm not going to change the defaults unless more people complain. (In reply to David Jarvie from comment #7) > You are the first user to complain about this in over 20 years, so I'm not > going to change the defaults unless more people complain. Everything has its first time. Unfortunately, the one who suffers is the end user with a developer who has the mind of a museum. You can't even see that even the UI is antiquarian. If you think it's good to eliminate alarms created by elderly users, children and teenagers, you are truly stupid. I hope you are removed from this project that needs to have people who think outside the box and not donkeys with a visor. Also, try to resolve others simple bugs that have been stuck in your hands for years. If you do not feel obliged to solve it, leave the task so that another volunteer can take on the task. I wanted to recommend scaling back the comments and not move them into personal attacks. Our developers at Plasma understand the reasoning. It's important to remember that for our team, it's very important to know what users go through. However, when the lack of evidence to the contrary is absent, it's hard to make a global change in the system because of one piece of evidence. In our team, we are attentive to the users. If you have the ability to bring real examples and situations from real users about this issue, we can consider it more. If you have user experience information that can help us make a different decision, bring it to the team. We are happy to review. What we will not consider it personal attacks. Please scale back your comments and focus on the issues. |