D21531: Bug fix in Scheduler for pausing after capturing sequence
noreply at phabricator.kde.org
Sun Jun 2 15:13:34 BST 2019
wreissenberger added a comment.
I guess you do not mean the bug fix part. For this the use case is very simple: "I want it working :-)"
In addition, I want it being visible when the pausing state is reached. In fact, we have two stages: "pausing" and "paused". By pressing the pause button, we enter the stage "pausing". This is especially visible in the case that the pausing button has been pressed during a capture sequence. In this case, the Scheduler waits until the capturing sequence is completed. As soon as the capturing sequence is completed, the Scheduler reaches the state "paused".
To visualize this, during the "pausing" stage the pause button is inactive. As soon as the "paused" stage has been reached, the pause button gets checked and obtains a red background.
My intention for this diff is delivering a minimal set so that pausing the Sequencer works properly. Having this in place, I could continue the Observatory diff D21291 <https://phabricator.kde.org/D21291> and add a communication from the Observatory that pauses the Scheduler in case of warnings and stops it in alert case.
From a mid term perspective I would like to go further:
- Should pausing of the Scheduler trigger pausing of Capture? Currently it waits until sequence completion.
- Is it really necessary having both sleeping and pausing capabilities in parallel? Sleeping is invoked when Scheduler wants to wait for the current job's starting time to be reached. Pausing does more or less the same without having a defined end.
- The status messages of the SchedulerJob are slightly misleading when the Scheduler is paused.
Does that answer your question?
To: wreissenberger, mutlaqja, TallFurryMan
Cc: kde-edu, narvaez, apol
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the kde-edu