https://bugs.kde.org/show_bug.cgi?id=400265
Bug ID: 400265
Summary: Schedule with single frame capture does not initiate
meridian flip
Product: kstars
Version: 3.0.1
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: mutla...@ikarustech.com
Reporter: wreis...@gmx.de
Target Milestone: ---
SUMMARY
Meridian flips are not initiated if a sequence has only one single frame
captured - no matter how often the schedule repeats the sequence.
STEPS TO REPRODUCE
1. Create a capture sequence with only one single light frame
2. Create a schedule with this sequence, select a star close before meridian
and set the schedule to "repeat until terminated"
3. Start the schedule before the target crosses the meridian.
OBSERVED RESULT
Even if the target crosses the meridian, a meridian flip is never initiated.
EXPECTED RESULT
As soon as the star has crossed the meridian, the next new frame capture leads
to a meridian flip before the frame capture is started.
SOFTWARE VERSIONS
2.9.8 as well as 3.0.0
KDE Frameworks Version: 5.28.0
Qt Version: 5.7.1
ADDITIONAL INFORMATION
This happens only for sequences contain one single frame. As soon as the
sequence contains more than one single frame (e.g. LRGB), the meridian flip is
running fine.
The reason behind is, that in processJobCompletion() it is checked if
getPendingJobCount() > 0 before checkMeridianFlip() is called. For a single
capture this makes sense. In case that a sequence is contained in a schedule
that repeats this schedule, this restriction does not make sense.
--
You are receiving this mail because:
You are watching all bug changes.
