D14942: Connect new-image event to Scheduler imaging time estimator.

[Wolfgang Reissenberger]

wreissenberger added a comment.


  Do we really to consider what happens on the storage? I would simply count a frame if it has been stored successfully. If it disappears at a later stage, why should we care?
  
  I personally tend to move captured images during a the night from my raspberry pi to my NAS storage while the camera is shooting. I would prefer if the scheduler simply counts captured frames, no matter whether they still sit on the place where they have been stored originally.
  
  Maybe it is the easiest way to keep all job counts in the memory as long as EKOS is running. After a reset, all counts should be set to zero.
  
  Too radical?

REPOSITORY
  R321 KStars

BRANCH
  improve__scheduler_image_update (branched from master)

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

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