Audacious - OLD, PLEASE USE GITHUB DISCUSSIONS/ISSUES

I should mention that right now, inadvertently it seems, hitting the Pause button twice will have essentially the same effect as a Play/Pause toggle.

If I were to tackle this feature myself, how should I approach it? I looked already at `ui_gtk.cc` though it's not yet perfectly clear to me how the toggle is being achieved there (there is only `button_play` and no `button_pause` there). And I looked at `statusicon.cc`, but it's not obvious to me how to the Play and Pause buttons into a toggle...

Adding support for "dynamic" menus wouldn't be a good task for a new contributor since there will be some API design involved. If you're interested in contributing in other areas, there are still some missing features in the Qt UI that need to be ported. I would be thrilled to see pull requests for some of those.

Liviu Andronic wrote:

I should mention that right now, inadvertently it seems, hitting the Pause button twice will have essentially the same effect as a Play/Pause toggle.

That's intentional. The "Pause" command is really pause/unpause. And "Play" is not identical to unpause, so the two are not redundant.

John Lindgren wrote:

The "Pause" command is really pause/unpause. And "Play" is not identical to unpause, so the two are not redundant.

I think I understand now. From what I see, there are three possible 'initial' states:
- stopped
- playing
- paused

The current arrangement seems to work like this:
- Play will start playing the track from the beginning if 'stopped' or 'playing', and resume playing the track if 'paused'
- Pause will pause the track if 'playing', resume playing the track if 'paused', and do nothing if 'stopped'
- Stop will stop the track if 'playing' or 'paused', and do nothing if 'stopped'

For me the arrangement is still somewhat confusing, especially Pause acting as a Play/Pause toggle (with no dynamic icon change) and Pause being available when 'stopped'.

In principle 'playing' and 'paused' are mutually exclusive states, which is why having a Play/Pause toggle would make sense. So the proposed arrangement would work like this:
- Play will start playing the track from the beginning if 'stopped', and resume playing the track if 'paused'
- Pause will pause the track if 'playing'
- Stop will stop the track if 'playing' or 'paused', and do nothing if 'stopped' (same as before)

Overall this seems to greatly simplify the logic of the Play/Pause arrangement and make it more intuitive. If the user wants to start the track from the beginning when currently 'playing', we can reasonably expect them to first hit Stop then Play -- it seems like this would remain the only usecase that wouldn't be covered directly by a single menu item.