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

Add ability to toggle the explicit content filter #524

Closed

Conversation

mpolyakova
Copy link

This adds the ability to toggle the explicit content filter using 'f' as a shortcut. This was requested in #506.

Unfortunately I was not able to use the user.changeSettings method and was getting a code 9 error back. It wasn't very clear which key it was expecting. user.setExplicitContentFilter works fine though! 😄

I hesitated from having PIANO_REQUEST_GET_SETTINGS fill in all the data in the relevant places, or adding a new struct with unused fields, instead only filling the new PianoRequestDataGetExplicitContentFilterInfo_t struct. Thoughts?

@PromyLOPh
Copy link
Owner

Unfortunately I was not able to use the user.changeSettings method
and was getting a code 9 error back. It wasn't very clear which key it
was expecting.
Can you upload the code? Maybe we can figure out what is missing.

PromyLOPh added a commit that referenced this pull request Aug 10, 2015
Currently exposed settings: Username, password and explicit content
filter. New key for settings is ‘!’, changeable with “act_settings”.

Fixes issues #524 and #506.
@PromyLOPh PromyLOPh closed this Aug 10, 2015
fawaf pushed a commit to fawaf/pianobar that referenced this pull request Aug 19, 2016
Currently exposed settings: Username, password and explicit content
filter. New key for settings is ‘!’, changeable with “act_settings”.

Fixes issues PromyLOPh#524 and PromyLOPh#506.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants