https://bugs.kde.org/show_bug.cgi?id=397776
Wolfgang Reissenberger <wreis...@gmx.de> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |WORKSFORME
Status|CONFIRMED |RESOLVED
--- Comment #2 from Wolfgang Reissenberger <wreis...@gmx.de> ---
OK, I see, works as designed, and I fully agree, we should not add more
complexity to the current scheduler.
Meanwhile, I found a scheduler setup that is more robust and leads to the same
capturing behavior.
Instead of defining one job with an end time and another one with this time as
start time, I use
- the first job with a defined end time
- a second job with a higher priority value and ASAP as startup time.
Since the first has higher priority, it will be executed until it reaches the
end time. The second one won't start unless the end time has passed.
Both jobs will restart in case that they have been aborted - so we have a more
robust job schedule than before.
I will set the status to "resolved/worksforme"
--
You are receiving this mail because:
You are watching all bug changes.
