Bug 398466 - No delay before first image possible
Summary: No delay before first image possible
Status: RESOLVED INTENTIONAL
Alias: None
Product: kstars
Classification: Applications
Component: general (show other bugs)
Version: 2.9.8
Platform: unspecified All
: NOR wishlist
Target Milestone: ---
Assignee: Jasem Mutlaq
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-09-10 17:04 UTC by Wolfgang Reissenberger
Modified: 2021-09-14 10:45 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Wolfgang Reissenberger 2018-09-10 17:04:02 UTC
The capture module has the option to set a delay. But this is only between two consecutive captures in the same sequence job.

I would like to have it *before* a capture takes place and not afterwards. For example, if you want to shoot one frame per filter every 1 minute directed by the scheduler, this is not possible. Instead, the capture module shoots as fast as possible.

There is another thing not possible: you cannot delay a capture after filter change, because exactly the first one after the change is shot immediately.

Or is there another I did not discover yet?
-Wolfgang
Comment 1 Jasem Mutlaq 2018-09-11 14:36:26 UTC
Right, the delay is working as intended (between captures). To support more delays, it has to be reworked.