D20029: Capture counting corrected

Eric Dejouhanet noreply at phabricator.kde.org
Wed Mar 27 17:28:05 GMT 2019


TallFurryMan added a comment.


  In D20029#439409 <https://phabricator.kde.org/D20029#439409>, @wreissenberger wrote:
  
  > Well, filling the map in any cases will not help, because the intention of **not** ticking "Remember progress" is exactly, that we start counting from zero - no matter how many are in the file system.
  
  
  No! Not remembering job progress means that we do not update the frame count from storage in the scheduler. It does not mean that we start from zero each time in the scheduler. We do, however, start from zero when executing a sequence job when not remembering progress. We still count frames captured at the scheduler job level.
  
  > The core problem is, that we do not count captures on single capture sequence level. As a consequence, we are not able to calculate the remaining capture time. It simply is quite tricky... I will dig into it the next days...
  
  Agreed, that's what I propose to do in my previous post. Counting frames when they are emitted by the capture module.

REPOSITORY
  R321 KStars

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

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


More information about the kde-edu mailing list