https://bugs.kde.org/show_bug.cgi?id=396182
TallFurryMan <eric.dejouha...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |WAITINGFORINFO
Status|UNCONFIRMED |NEEDSINFO
--- Comment #1 from TallFurryMan <eric.dejouha...@gmail.com> ---
I agree on adding a settings option to the Capture module to allow manual
change of a filter.
If such option is set, a pop-up requesting the change would block the Capture
module for the end-user to run the change, as stated in point 3 from the OP.
Point 1 can be handled with the Filter Wheel Simulator with no implementation
change, as long as the request to the end-user is made before requesting the
Simulator to change the filter (because that changes the state of the Capture
module too soon). It is the responsibility of the end-user to configure the
filter names in the Filter Wheel Simulator so that they match the sequence
because that has an impact on capture storage files, as mentioned in point 1
from the OP. Proper numbering of the filter on the wheel is not needed, but is
recommended for clarity.
Point 3 is already covered if we use the Filter Wheel Simulator.
Point 4 cannot be achieved, but actually only the Capture module requires
operations to be blocked. That's probably what the OP meant anyway.
Default value must be disabled, no blocking of the Capture module for manual
filter change.
Location of the option in the UI is not easy. We need an option that pertains
to the Capture module, and related to the filter, so the first idea would be to
implement it with a checkbox in the Filter Settings, under the focus offset
table. While it might be easily forgotten here, the fact that a pop-up would
remind the end-user of this option is probably enough.
Open question: in the implementation, are filter offsets relevant for a single
filter selection, or general to all filters?
Open question: would it be interesting to have the feature even for automated
filter wheels, to allow tinkering in that case too? (nothing in this post
suggestions prevents this)
--
You are receiving this mail because:
You are watching all bug changes.
