On 2009/03/25 22:46, Jeffrey Middleton <jefr...@gmail.com> wrote: > 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.
Let's wait if any client developer responds to your question. I cannot imagine why this feature might be useful. If it's broken and nobody uses it, we can safely remove it. Max ------------------------------------------------------------------------------ _______________________________________________ Musicpd-dev-team mailing list Musicpd-dev-team@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/musicpd-dev-team
