Summary: | kalarm a new alarm, a disaster when you click Modify | ||
---|---|---|---|
Product: | [Applications] kalarm | Reporter: | fizista |
Component: | general | Assignee: | David Jarvie <djarvie> |
Status: | CLOSED FIXED | ||
Severity: | crash | ||
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Unlisted Binaries | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
fizista
2009-11-06 20:04:35 UTC
Could you please describe exactly what you were doing at the time of the crash, or what KAlarm was doing. It looks as if you clicked on the Edit button in an alarm message window, and that the same alarm triggered again while you were still editing the alarm - please confirm if that is what happened. I created a new alarm. I've set the delay except for 1 hour (I think). Then - OK. Immediately displays the alarm me. I wanted to modify it (kalarm crash). I can not repeat this mistake. Maybe I did something I do not remember what. This crash is due to the alarm window (which is the parent of the edit dialogue) being closed or replaced while the dialogue is still open. There are two things which need to be done to fix this: - change the alarm window's contents instead of closing it and displaying a new one when it changes from a reminder to a normal alarm, or when the final trigger occurs for a repeat-at-login alarm. - when the alarm window closes, change the edit dialogue's parent window to the KAlarm main window. Fixed first case, where the alarm window's contents change (SVN commits 1050233, 1050234). Fixed other case, when the alarm window auto-closes while an edit dialog is open (SVN commits 1052909, 1052910). Additional commits for the first case: 1050333, 1050335, 1051193, 1051194. |