https://bugs.kde.org/show_bug.cgi?id=462812
Bug ID: 462812
Summary: make abort and start buttons separate in imaging
module
Classification: Applications
Product: kstars
Version: 3.6.0
Platform: Other
OS: Linux
Status: REPORTED
Severity: wishlist
Priority: NOR
Component: general
Assignee: mutla...@ikarustech.com
Reporter: sequel.county...@icloud.com
Target Milestone: ---
SUMMARY
***
The stop/abort button is in the same place on the screen as the go button with
the function changing depending upon whether images are being taken or not.
Unfortunately when you abort a sequence it’s not instant and there’s no
feedback to show that you’ve actually pressed it. This leads the user to try
pressing the abort button again, shortly after this it changes to the go button
which gets the click and sets the sequence going again. So the user clicks
abort and…..
Separating the buttons on the screen would prevent this annoying cycle.
Also when you are using a vnc from a touch screen device like an ipad it would
make you more confident that you aren’t going to accidentally abort things when
you go to touch the screen to move the pointer to a different location
***
STEPS TO REPRODUCE
1. Set image sequence going
2. Decide to abort it for some reason and click the button
3. Nothing appears to happen click it again
OBSERVED RESULT
abort happens, button becomes go button, second click triggers that and the
sequence starts again
EXPECTED RESULT
abort happens and you don’t accidentally trigger things off again
SOFTWARE/OS VERSIONS
Windows:
macOS:
Linux/KDE Plasma:
(available in About System)
KDE Plasma Version:
KDE Frameworks Version:
Qt Version:
ADDITIONAL INFORMATION
I’m on astroberry using vnc to connect from an ipad over wifi but this is
probably relevant for all setups
--
You are receiving this mail because:
You are watching all bug changes.
