- 28 Nov, 2013 1 commit
-
-
Max Kellermann authored
-
- 21 Oct, 2013 3 commits
-
-
Max Kellermann authored
Fixes regression from commit e96779de.
-
Max Kellermann authored
-
Max Kellermann authored
Leave that to the caller, allowing it to modify multiple items at a time.
-
- 19 Oct, 2013 2 commits
-
-
Max Kellermann authored
-
Max Kellermann authored
-
- 28 Jul, 2013 1 commit
-
-
Max Kellermann authored
-
- 08 Jan, 2013 7 commits
-
-
Max Kellermann authored
-
Max Kellermann authored
-
Max Kellermann authored
-
Max Kellermann authored
The check for unsigned underflow is fragile and unreliable.
-
Max Kellermann authored
-
Max Kellermann authored
-
Max Kellermann authored
-
- 07 Jan, 2013 3 commits
-
-
Max Kellermann authored
-
Max Kellermann authored
-
Max Kellermann authored
-
- 06 Jan, 2013 3 commits
-
-
Max Kellermann authored
-
Max Kellermann authored
-
Max Kellermann authored
-
- 04 Jan, 2013 1 commit
-
-
Max Kellermann authored
-
- 21 Aug, 2012 1 commit
-
-
Max Kellermann authored
-
- 15 Aug, 2012 1 commit
-
-
Max Kellermann authored
Make sure the queue "owns" all song objects, so nobody else can free them.
-
- 18 Jul, 2011 1 commit
-
-
Max Kellermann authored
Sorts remaining songs by priority. This can be used for the much-demanded "queue feature".
-
- 29 Jan, 2011 1 commit
-
-
Max Kellermann authored
-
- 31 May, 2010 1 commit
-
-
Romain Bignon authored
-
- 16 Jan, 2010 1 commit
-
-
Max Kellermann authored
Check consume mode in queue_next_order(), because the current song would be deleted as soon as it's finished; it cannot be played again.
-
- 01 Jan, 2010 1 commit
-
-
Avuton Olrich authored
-
- 12 Nov, 2009 1 commit
-
-
Max Kellermann authored
After we've been hit by Large File Support problems several times in the past week (which only occur on 32 bit platforms, which I don't have), this is yet another attempt to fix the issue.
-
- 13 Oct, 2009 1 commit
-
-
Max Kellermann authored
Renamed idToPosition.
-
- 30 Mar, 2009 2 commits
-
-
Avuton Olrich authored
-
Romain Bignon authored
Consume mode removes each song played
-
- 27 Mar, 2009 2 commits
-
-
Romain Bignon authored
When single mode is enabled, after current song it stops playback, or it replay same song if repeat mode is activated.
-
Romain Bignon authored
The smartstop feature is a way to tell mpd to stop playing after current song. This patche provides: - 'state' command returns 'smartstop' state (1 or 0) - 'smartstop' can activate or not the smartstop state - when song is terminated, mpd stops playing and smartstop is set to 0
-
- 26 Mar, 2009 1 commit
-
-
Jeffrey Middleton authored
The move command now accepts a range for the first argument, in the same form as other range commands, e.g. move 15:17 3. The first song in the range is placed at the destination position. Note that as with other range commands, the range is inclusive on the left only; this example would move only songs 15 and 16, not 17. [mk: fixed signed/unsigned warnings; use G_MAXUINT instead of UINT_MAX]
-
- 13 Mar, 2009 1 commit
-
-
Avuton Olrich authored
This updates the copyright header to all be the same, which is pretty much an update of where to mail request for a copy of the GPL and the years of the MPD project. This also puts all committers under 'The Music Player Project' umbrella. These entries should go individually in the AUTHORS file, for consistancy.
-
- 09 Feb, 2009 1 commit
-
-
Max Kellermann authored
Commit f78cddb4 introduced a regression: after a song was moved, the order array was not updated (in random mode). This caused MPD to think the "current" song has changed when you moved something to the position of the current song.
-
- 25 Jan, 2009 1 commit
-
-
Max Kellermann authored
This function shuffles the last song of a range. This is used by addSongToPlaylist().
-
- 23 Jan, 2009 1 commit
-
-
Max Kellermann authored
This patch fixes a regression introduced by commit aa9ffc.
-
- 22 Jan, 2009 1 commit
-
-
Max Kellermann authored
The function shuffles the virtual order of songs, but does not move them physically. This is used in random mode. The new function replaces playlist.c's randomizeOrder() function, which was aware of playlist.current and playlist.queued. The latter is always -1 anyway, and the former as preserved by the caller, by converting playlist.current to a position, and then back to an order number.
-