Bug 302001 - Reminder on task to "display a dialog . . . before the todo starts" takes this as meaning ". . . ends"
Summary: Reminder on task to "display a dialog . . . before the todo starts" takes th...
Status: RESOLVED UNMAINTAINED
Alias: None
Product: korganizer
Classification: Applications
Component: reminder daemon (korgac) [CLOSED: Use Reminder Daemon product] (other bugs)
Version First Reported In: 4.8.x
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-06-16 09:06 UTC by Graham P Davis
Modified: 2017-01-07 22:47 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Graham P Davis 2012-06-16 09:06:47 UTC
The reminder that had been set to appear before a task started waited until it had almost finished before appearing.

Reproducible: Always

Steps to Reproduce:
1. Create task.
2. Remove default reminder
3. Select reminder to  "display a dialog one hour before the todo starts"
Actual Results:  
Reminder appeared one hour before the task ended.

Expected Results:  
Reminder should have appeared one hour before the task started.
Comment 1 Sergio Martins 2013-09-07 19:05:15 UTC
Can you re-test with 4.11.2 when it's out ?
Comment 2 Denis Kurz 2016-09-24 18:49:50 UTC
This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present?

If noone confirms this bug for a Framework-based version of korganizer (version 5.0 or later, as part of KDE Applications 15.08 or later), it gets closed in about three months.
Comment 3 Graham P Davis 2016-09-24 20:03:34 UTC
I see I neglected a request for info a few years ago; sorry about that. It could be that I'd already stopped using the application but I still should have said so at the time. I have no info as to whether the bug still exists; sorry.
Comment 4 Denis Kurz 2017-01-07 22:47:59 UTC
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input.