Pause behaviour

[Björn]

Hi,

I'm tinkering with pause/resume and I was wondering what kind of
behaviour we want when jumping to the next or previous file while
paused. We can:
* Ignore previous/next
* Jump to the file and start playing
* Jump to the file and stay paused

Which option would match the expectations of the users?

FYI, stopping while paused is possible.

Björn

[casey....@gmail.com]

I expect it to jump to the next track and stay paused.

Stopping while paused also makes sense. Some people will argue that
stop and pause should mean the same thing, I disagree. Stop should
reset the transport to its default state, and close all open streams.

Casey

[Björn Olievier]

I'm thinking the same thing about stopping while paused.  This is exactly what happens.  When pressing pause, the audio threads are put on hold.  So all resources stay in use.  When stopping everything is cleaned up and closed down.

 

The play button is toggled between Play/Pause/Resume depending on the audio events received and buttons pressed.

 

Björn

[Julian Cromarty]

I would agree with Casey on the skipping while paused and that stopping while paused should be there and be a definite stop and clean up.

Jooles

2008/5/15 Björn Olievier <bjorn.o...@gmail.com>:

[casey....@gmail.com]

Also, while we're on the subject, the "Previous" button should rewind
the current track to the beginning if more than a few seconds has
expired. If less than a few seconds has expired it should start the
previous track. This is how hardware transports typically behave.

Casey

On May 15, 3:24 am, "Björn Olievier" <bjorn.oliev...@gmail.com> wrote:
> I'm thinking the same thing about stopping while paused.  This is exactly
> what happens.  When pressing pause, the audio threads are put on hold.  So
> all resources stay in use.  When stopping everything is cleaned up and
> closed down.
>
> The play button is toggled between Play/Pause/Resume depending on the
> audio events received and buttons pressed.
>
> Björn
>