On Tue, Mar 24, 2009 at 4:45 PM, Max Kellermann <m...@duempel.org> wrote:
> On 2009/03/24 16:26, Jeffrey Middleton <jefr...@gmail.com> wrote:
>
> > Anyway, I figure a moverange command is a reasonable thing to have within
> > mpd. I've written and tested the queue_move_range function which will be
> > behind it, but haven't dealt with the command parsing side yet. I figure
> it
> > should (like shuffle_range) use the same command, e.g. "move start:end
> to."
>
> Perfect!
>
While testing moving ranges, I ran into the move relative to current song
feature. The comments in the source say, for a command "move from to":
/*
* (to < 0) => move to offset from current song
* (-playlist.length == to) => move to position BEFORE current song
*/
However, these conditions seem to move to one past where they should. That
is, (to == -1) moves to two after the current song, and (-playlist.length ==
to) moves to one after the current song. From what I can tell, the behavior
for (to<0) hasn't changed since originally added, so I was wondering if
anyone's actually used this feature. I don't want to break clients by
fixing it, but I'm pretty sure it doesn't work as documented.
Jeffrey
------------------------------------------------------------------------------
_______________________________________________
Musicpd-dev-team mailing list
Musicpd-dev-team@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/musicpd-dev-team
