https://bugs.kde.org/show_bug.cgi?id=397561
Bug ID: 397561
Summary: Sequence jobs with "filter" suffix see less captures
than sequence jobs without
Product: kstars
Version: 2.9.7
Platform: Other
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: general
Assignee: mutla...@ikarustech.com
Reporter: eric.dejouha...@gmail.com
Target Milestone: ---
Created attachment 114467
--> https://bugs.kde.org/attachment.cgi?id=114467&action=edit
Session log, see the very end of the file for details
Consider the processing of two identical scheduler jobs, using similar sequence
jobs, capturing to the same storage folder, but one with "filter" suffix
enabled and one with "filter" suffix disabled.
When executed on a storage that already contains captures, the scheduler will
associate less of those captures to the sequence job that has "filter" suffix
enabled than to the sequence job that has "filter" suffix disabled.
This happens because the capture recognition is processed by checking the
beginning of the string. The sequence job without the "filter" suffix will
match the captures with the "filter" suffix, but the sequence job with the
"filter" suffix will not match the captures without the "filter" suffix.
--
You are receiving this mail because:
You are watching all bug changes.
