https://bugs.kde.org/show_bug.cgi?id=398635
Bug ID: 398635
Summary: When capture suspends because of guiding deviation,
and capture is stopped, UI is in invalid state
Product: kstars
Version: git
Platform: Other
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: general
Assignee: mutla...@ikarustech.com
Reporter: eric.dejouha...@gmail.com
Target Milestone: ---
When capturing a target, it may happen than guiding deviation suspends the
capture until the guide star is repositioned to the lock position. If the
Capture module is stopped by the Scheduler at that moment (programmatically as
opposed to through the UI), the Capture module enters a weird state where the
start/stop icon expectedly displays as a "start", but where it is not possible
to load a new sequence or request a preview.
Clicking the "start" button at that moment reveals that the state of the module
is actually still "capturing" although no capture is taking place or can take
place anymore. After clicking, the "start" button remains in state "start", but
suddenly features are working again.
This seems to be a side-effect or regression of the introduction of the suspend
state. Stopping the capture programmatically doesn't restore the initial
configuration.
--
You are receiving this mail because:
You are watching all bug changes.
