Bug 139864 - "Stop after current" to change position to next song after finished
Summary: "Stop after current" to change position to next song after finished
Status: RESOLVED DUPLICATE of bug 133490
Alias: None
Product: amarok
Classification: Applications
Component: general (show other bugs)
Version: 1.4.3
Platform: unspecified Linux
: NOR wishlist
Target Milestone: ---
Assignee: Amarok Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-01-10 16:19 UTC by munlinux
Modified: 2007-10-05 19:00 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description munlinux 2007-01-10 16:19:00 UTC
Version:           1.4.3 (using KDE 3.5.5, Kubuntu (dapper) 4:3.5.5-0ubuntu1~dapper2)
Compiler:          Target: i486-linux-gnu
OS:                Linux (i686) release 2.6.15-27-386

As per bug 127312 AmaroK was made to remember songlist position after using the "Stop after current" -command. However, the current implementation (v. 1.4.3) does not advance the songlist position (regardless of whether we are using linear or random playmode) after stopping this way. Thus, if you use "stop after current", and later in the day press play again to continue where you'd left off, you end up hearing the same song twice. IMO it would be better if this didn't occur, and the playlist would switch to a next song after stopping. Conceivably a bug, but so minor that I labeled this as wishlist.
Comment 1 munlinux 2007-01-26 11:07:06 UTC
Let me be more precise on this one - the songlist position _is_ actually advanced by one in _linear mode_. So, this is only an issue for the random modes.
Comment 2 Kevin Funk 2007-02-05 13:42:23 UTC
Seems to work in 1.4.4 by now. Please upgrade and verify this.
Comment 3 Chris Peikert 2007-02-25 01:35:52 UTC
I'm running 1.4.4, and this bug is still there.  I choose "stop after current track," track finishes, I press play, and the same track starts again.  This is in random mode.
Comment 4 shattered 2007-08-28 21:36:43 UTC
dup of bug 133490
Comment 5 Harald Sitter 2007-08-28 23:12:41 UTC

*** This bug has been marked as a duplicate of 133490 ***
Comment 6 munlinux 2007-10-05 19:00:06 UTC
Transferred my votes for the earlier report. (That report was in the "closed" state at the time this report was filed.)