mirror of
https://github.com/librespot-org/librespot.git
synced 2026-04-27 08:15:50 +03:00
Labels
No labels
A-Alsa
SpotifyAPI
Tokio 1.0
audio
bug
can't reproduce
compilation
dependencies
duplicate
enhancement
good first issue
help wanted
high priority
imported
imported
invalid
new api
pull-request
question
reverse engineering
wiki
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/librespot#900
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
📋 Pull Request Information
Original PR: https://github.com/librespot-org/librespot/pull/386
Author: @willstott101
Created: 10/19/2019
Status: ✅ Merged
Merged: 2/13/2020
Merged by: @sashahilton00
Base:
dev← Head:cha_cha_shuffle📝 Commits (1)
8b80326Fix shuffle and repeat when changing contexts to match Android behaviour📊 Changes
1 file changed (+10 additions, -2 deletions)
View changed files
📝
connect/src/spirc.rs(+10 -2)📄 Description
Seems strange that these fields return true in the has_ methods when as far as I can tell it's impossible to remove the shuffle/repeat state in the client without explicitly toggling them with their dedicated buttons.
@devgianlu You mention in #266 that that librespot-java might handle this better, (I couldn't get it to work with Zeroconf on my windows laptop, I'll try again later), but browsing the code I couldn't see anything like this so I'm curious if the shuffle state does actually work better over there? Perhaps you've found a better solution.
EDIT: It would be great if a few people could try this out and see if they can get inconsistent behaviour between an official client and Librespot with these changes.
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.