[PR #172] [MERGED] Save/restore queue behavior #445

Closed
opened 2026-02-28 14:33:02 +03:00 by kerem · 0 comments
Owner

📋 Pull Request Information

Original PR: https://github.com/jpochyla/psst/pull/172
Author: @aeons
Created: 9/7/2021
Status: Merged
Merged: 9/16/2021
Merged by: @jpochyla

Base: masterHead: save-restore-queue-behavior


📝 Commits (1)

  • 2f8fe67 Save/restore queue behavior

📊 Changes

4 files changed (+19 additions, -4 deletions)

View changed files

📝 psst-gui/src/controller/playback.rs (+1 -1)
📝 psst-gui/src/data/config.rs (+3 -1)
📝 psst-gui/src/data/mod.rs (+7 -1)
📝 psst-gui/src/data/playback.rs (+8 -1)

📄 Description

This PR...

  • adds queue behavior to the configuration
  • updates and saves the configuration on queue behavior changes
  • and restores the queue behavior state on startup

Currently it handles all queue behaviors, but it might make sense to only restore sequential/random (which is my use case), since loop track and loop all are more used on a once-off basis?


🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/jpochyla/psst/pull/172 **Author:** [@aeons](https://github.com/aeons) **Created:** 9/7/2021 **Status:** ✅ Merged **Merged:** 9/16/2021 **Merged by:** [@jpochyla](https://github.com/jpochyla) **Base:** `master` ← **Head:** `save-restore-queue-behavior` --- ### 📝 Commits (1) - [`2f8fe67`](https://github.com/jpochyla/psst/commit/2f8fe67be2b9975d8f26bd9b387585317049e7ba) Save/restore queue behavior ### 📊 Changes **4 files changed** (+19 additions, -4 deletions) <details> <summary>View changed files</summary> 📝 `psst-gui/src/controller/playback.rs` (+1 -1) 📝 `psst-gui/src/data/config.rs` (+3 -1) 📝 `psst-gui/src/data/mod.rs` (+7 -1) 📝 `psst-gui/src/data/playback.rs` (+8 -1) </details> ### 📄 Description This PR... - adds queue behavior to the configuration - updates and saves the configuration on queue behavior changes - and restores the queue behavior state on startup Currently it handles all queue behaviors, but it might make sense to only restore sequential/random (which is my use case), since loop track and loop all are more used on a once-off basis? --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
kerem 2026-02-28 14:33:02 +03:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/psst#445
No description provided.