CamiJolly1 commented 10 months ago

User Story

Essential components

[x] Title describes the story
[x] Stakeholder type is identified
[x] Outcome is described
[x] Rationale is explicit
[ ] Acceptance criteria are verifiable and from the perspective of the stakeholder

Story

As a user I want a stop button so that I am able to stop the music when desired instead of having to close the application.

Acceptance Criteria

There is a user interface input element that indicates selecting it will stop currently playing sound
Selecting at element stops the currently playing sound rendering

Supporting Information

At present, when a user opens an image and starts audio rendering, the "music" only stops when it reaches the end of the image data or the program is halted. Closing the image window does not interrupt the audio rendering so the music will continue to play. Adding a "stop playing" control would allow the user to stop the music when they want to.

Note that the meaning of the "stop" control needs to be well-defined. For example, is "stop" associated with a particular image rendering, thus there would be multiple "stop" controls, each associated with a specific image being "played"? Is "stop" a global control that will interrupt all audio renderings that are currently playing? If "stop" is associated with a particular image, if the associated window is closed is the ability to "stop" lost? Does closing the visual rendering necessarily stop the audio rendering?

Dependencies

(Issues on which this story depends)

(Issues dependent on this story)

ramahali commented 10 months ago

I'd like to be assigned to this

CamiJolly1 commented 10 months ago

I would recommend this button be added under the play button.

jody commented 10 months ago

I replaced the word "button" with "control" so that a wider range of user interface elements can be considered. Note that "menu items" are currently the primary form of interaction within ImageLab.