1344: Stop after Current button (on player) issue [#7215]

Beta Testing for Windows Products and plugins

Moderator: Gurus

Mizery_Made
Posts: 2283
Joined: Tue Aug 29, 2006 1:09 pm
Location: Kansas City, Missouri, United States

1344: Stop after Current button (on player) issue [#7215]

Post by Mizery_Made »

I've found that the Stop after Current button on the player (of those skins that have them) doesn't always work the first time it's pressed. It doesn't seem to be every time that it fails (meaning there are times where the first press does work), however it seems to fail more times than not. I noticed it when I checked the entry for the feature under the Play menu, and saw that it wasn't indicating the feature was on, despite having just played it. A second pressing of the button on the player then proceeded to enable it in the menu.

I figured it may have just been "mis-communication" (if you will) between those two places. However, this isn't a UI issue as on further testing, when the player button is pressed but it appears disabled on the Play menu... the player moves to the next track and continues playing. So it seems to be a matter of the player button not always correctly enabling the feature. Seems to only occur on the first attempt after a song plays, toggling several times after seems to work fine. Haven't tested extensively however.

Anyone else see this behavior?
Lowlander
Posts: 58851
Joined: Sat Sep 06, 2003 5:53 pm

Re: 1344: Stop after Current button (on player) issue

Post by Lowlander »

I could reproduce:

1) Play song
2) Use Stop after current on player
3) Click Stop after current in Play menu (disabling it)
4) Use Stop after current on player

Notice it isn't enabled in the Play menu or:

1) Play song
2) Use Stop after current on player
3) Click Stop after current in Play menu (disabling it)
4) Click Stop after current in Play menu (enabling it)
5) Use Stop after current on player

Notice it isn't disabled in the Play menu.

So it seems that after using Stop after current in the Play menu the next Stop after current button press in the Player is ignored.
Mizery_Made
Posts: 2283
Joined: Tue Aug 29, 2006 1:09 pm
Location: Kansas City, Missouri, United States

Re: 1344: Stop after Current button (on player) issue

Post by Mizery_Made »

What I'm seeing here is:

1) Play song
2) Press "Stop after Current Track" button on the player
3) Look at (don't press) the entry for this feature on the Play menu; see that it displays as if it's not enabled
4) Let track play until the end; it moves onto the next track and continues to play

or

1) Play song
2) Press "Stop after Current Track" button on the player
3) Look at (don't press) the entry for this feature on the Play menu; see that it displays as if it's not enabled
4) Press "Stop after Current Track" button on the player a second time
5) Look at (don't press) the entry for this feature on the Play menu; see that it now displays as if it's enabled
6) Let track play until the end; it moves onto the next track and correctly stops playback

I haven't tried your steps (as it's late, and I'm already exhausted as I'm a little under the weather), but I think it goes to show that there's a general issue with the button. I believe you can substitute the "Play -> Stop after Current Track" button with the "Stop after Current Track" toolbar button as well and see the same behavior.
Lowlander
Posts: 58851
Joined: Sat Sep 06, 2003 5:53 pm

Re: 1344: Stop after Current button (on player) issue

Post by Lowlander »

I think your steps are the same issue, just exhibited in reverse. I've entered it here: http://www.ventismedia.com/mantis/view.php?id=7215
Lowlander
Posts: 58851
Joined: Sat Sep 06, 2003 5:53 pm

Re: 1344: Stop after Current button (on player) issue [#7215

Post by Lowlander »

I can no longer reproduce the issue on 1345, is it the same for you Mizery_Made?
Mizery_Made
Posts: 2283
Joined: Tue Aug 29, 2006 1:09 pm
Location: Kansas City, Missouri, United States

Re: 1344: Stop after Current button (on player) issue [#7215

Post by Mizery_Made »

Looks to be fixed here as well, based on my quick tests.
Post Reply