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
Remove 'Enqueue downloaded' setting (always enqueue upon successful download) #6837
Comments
This issue has been mentioned on AntennaPod Forum. There might be relevant details there: https://forum.antennapod.org/t/new-episode-action-enhancement/3871/1 |
This sounds like you are also against adding an option to "do not add playing episodes to the queue" #4339, right? |
No, not necessarily against that. Actually, this makes me think: it is indeed a valid scenario: manually curate a queue, download or play something that's unrelated to the queue and not want that added to the queue. At the same time: how many users actually manually curate their queue, how many don't use the queue, and how many just let auto-download fill the queue? I somehow feel that few people manually curate queues, in which case both settings are not necessary.
But if we keep this setting, I would be in favour of having a single 'Enqueue downloaded and played' setting (rather than two separate ones).
I think that #1519 can be closed (and #3142 can remain closed):
|
Checklist
App version
3.2.0
Where did you get the app from
Google Play
Problem you may be having, or feature you want
We have a lot of settings. I can't think of a use case where this setting must be disabled. Having this setting adds another variable in the process of where episodes show up. And the queue is the
Suggested solution
Remove 'Enqueue downloaded' setting, and always enqueue upon successful download. Note that this doesn't mean that all downloads must be in the queue at all times (episode can be removed from Queue again after download).
Screenshots / Drawings / Technical details
To ensure we're not making a wrong change here, I would suggest implementing in three steps:
The text was updated successfully, but these errors were encountered: