Details
-
Suggestion
-
Resolution: Unresolved
-
P2: Important
-
None
-
6.4.3, 6.5.4
Description
According to suggestion from bartlomiejmoskal:
You would like to be able to control CaptureSession by additional function/property. Maybe something like "bool active" property and start/stop functions (I would prefer "start" rather than "record". "record" sounds like permanently saving the output). Of course, we take into account the suggestions of developers. If you would like to create such suggestion please create new Bug with correct title and description.
So, I create an issue for requesting adding bool active property, start() and stop() functionality for enabling explicit control of CaptureSession capturing and streaming capabilities.
It is super unconventional that whether capture is on or off is controlled by setting/unsettingĀ input/output - any? both? you see, it is far from being intuitive - devices.
As a developer if I have to dig into documentation in such details for such simple( ? ) functionality, it will clearly indicate there are usability issues with the component...
See, we were grown up with devices having dedicated play/stop/record buttons and not just attaching/detaching input and/or audio devices...
E.g. when one creates a megaphone app - - there are dedicated UI elements for selecting input and output devices and one(s) for controlling recording/streaming state. These UI elements can be in the same or different page...
If there is no record/stop function available controlling recording and streaming of medium but this setting/unsetting thingy then app will have to remember what input/output devices were selected by the user instead of just calling record()/stop() on CaptureSession item...
Fingers crossed I was convincing enough and will be able to use the super new CaptureSession soon.