We need to do some bookkeeping inside the Playlist before notifying the
Factory that a track has been requested.
Signed-off-by: Anna Schumaker <Anna@NoWheyCreamery.com>
This property is updated whenever the items in the Playlist change or if
the current-track property is changed. It can be used to know in advance
if calling next_track() can be expected to return a valid Track
instance.
Signed-off-by: Anna Schumaker <Anna@NoWheyCreamery.com>
And add a "shuffle" property to the Playlist class. I use a TrackidSet
instance to keep track of which trackids have already been picked, and
to select a random trackid from the remaining options.
Signed-off-by: Anna Schumaker <Anna@NoWheyCreamery.com>
I add a "loop" property to the Playlist class that can be set to "None",
"Playlist", or "Track" (to match the MPRIS2 loop property). I can then
tune the behavior of next_track() based on how loop is configured.
Signed-off-by: Anna Schumaker <Anna@NoWheyCreamery.com>
This sets the current_trackid field on the database playlist object to
the trackid of the provided track.
Signed-off-by: Anna Schumaker <Anna@NoWheyCreamery.com>
The move_track_up() and move_track_down() functions are used to manually
arrange the tracks in a playlist.
Signed-off-by: Anna Schumaker <Anna@NoWheyCreamery.com>
This model builds on the TrackidModel to make it more Playlist and Track
focused instead of trackid centric.
Signed-off-by: Anna Schumaker <Anna@NoWheyCreamery.com>