D13347: Preparing for homogeneity with capture tab.

[Eric Dejouhanet]

TallFurryMan added a comment.


  Thanks. Yes, the immediate evaluation is wanted. The rationale is that the scheduler should be consistent, and should not display both non-evaluated and evaluated jobs as there is no way to differentiate them in the table. All jobs evaluate when the scheduler starts, so having some not evaluated when the user clicks the start button is a usability problem somehow. For instance, if a job is already complete with all captures stored, or if a job cannot schedule because of altitude, it's better to tell the user before starting.
  
  Extending on this, I want to evaluate all jobs periodically, so that the scheduler can't start with asap jobs that are already in the past. Currently the scheduler reorders those afterwards without problem, but it causes an unexpected change to the visible schedule and we don't want to surprise the user. Also, duration estimates are incorrect currently, and are causing reorders too when the real duration is larger than 5min and aborts the next jobs. I'll move the estimates for each step at a location the user can update (or possibly make the scheduler measure and learn that duration).

REPOSITORY
  R321 KStars

REVISION DETAIL
  https://phabricator.kde.org/D13347

To: TallFurryMan, mutlaqja
Cc: kde-edu, narvaez, apol
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kde-edu/attachments/20180605/890d8320/attachment.html>