Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Mark track as playing and add to history if changing track while paused. #1356

merged 4 commits into from Dec 29, 2015


Copy link

@jcass77 jcass77 commented Dec 6, 2015

Suggested fix for #1352

Replaces #1353 which was created against the wrong branch (I'm an idiot).

@@ -19,6 +19,10 @@ Bug fix release.

- MPD: Notify idling clients when a seek is performed. (Fixes: :issue:`1331`)

- Core: Fix :meth:`~mopidy.core.PlaybackController._change_track` to mark
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think the method name is relevant for the changelog, as it's a private method.

@jodal jodal added this to the v1.1.2 - Bugfixes milestone Dec 6, 2015
Copy link
Member Author

jcass77 commented Dec 7, 2015

I've implemented the changes as suggested by @jodal.

It may be worth considering whether resume should also handle unplayable tracks in the same way that play does. In other words, shouldn't there be a _resume that mirrors _play that also skips to the next track if the track that the user is trying to resume is unplayable?

def test_resume_does_nothing_if_track_is_unplayable(self):
self.core.playback.state = core.PlaybackState.PAUSED
self.assertEqual(self.core.playback.state, core.PlaybackState.PAUSED)
makes sense if we are trying to resume a track that has become unplayable since it was paused (?), but if the user does pause -> next -> resume should Mopidy not keep skipping until it finds a track that is playable just like stop -> next -> play would?

Copy link
Member Author

jcass77 commented Dec 20, 2015

@jodal, is there anything else that you would like to have done on this PR before it can be merged?

Copy link

adamcik commented Dec 28, 2015

Don't know if @jodal had anything to add but there is a merge conflict currently. If there isn't anything else we can probably also resolve that ourselves.

Copy link

jodal commented Dec 28, 2015

@adamcik I have nothing to add. I'll resolve the conflict and merge.

@jcass77 Regarding the resume case, it sounds like you're onto something. Can you open a separate issue to track it?

@jodal jodal self-assigned this Dec 28, 2015
Copy link
Member Author

jcass77 commented Dec 29, 2015

On the pause->next->resume issue: the way that this case is handled in 'develop' at the moment seems to be correct.

I've created a small PR #1377 to prove this point.

@jodal jodal merged commit 3cd3b45 into mopidy:release-1.1 Dec 29, 2015
jodal added a commit that referenced this pull request Dec 29, 2015
@jodal jodal added the A-core Area: Core layer label Dec 29, 2015
@jcass77 jcass77 deleted the fix/1352 branch January 2, 2016 14:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
A-core Area: Core layer
None yet

Successfully merging this pull request may close these issues.

None yet

3 participants