[Bug] Selecting/playing a song from offline list throws away the existing queue

[dumblob]

Acknowledgements

• I have searched the existing issues and confirmed that this is a new issue, not a duplicate or related to another open issue.
• I read the FAQ section and there's nothing mentioned about this issue.
• I have written a short but informative title.
• I have updated the app to the latest version. You can find the latest version here.
• I will fill out all the sections in this issue report.

Current Behavior

Selecting/playing a song from offline list throws away the existing queue (and instead it adds the selected song and all the hundreds of songs in the full offline playlist).

Expected Behavior

I wish only the songs which are not yet in the queue will get added instead of full unnecessary cleanup of the queue. Please note a special case - if the newly selected song is already in the queue, it should stay in the queue untouched (same position).

Rationale: the queue is a curated "playlist", frustrating to re-create over and over in case one just wanted to stop the current playing song and instead play another one without adding this other one to the queue whatsoever

Steps To Reproduce

1. open offline list
2. add 2 songs to the queue
3. then click on any song in the offline list (this will remove the 2 songs from step (2) from queue and replace them with all the hundreds of offline songs in unspecified order)

Musify Version

v10.1.1

Device And Operating System

Android 16, Motorola Razr 50 Ultra

Android Version You Use

Android 17

Additional Information

This is a continuation of the request #843 (comment) .

[dumblob]

An alternative to the "Expected behavior" above would be if each "batch overwrite" (i.e. more than 1 song added/removed in one go/tap/click) would first save the current queue as a brand new "offline playlist" (labeled with the current timestamp) and only then execute the batch operation. Together with this it would be nearly necessary to add a way to make queue from a playlist.

[gokadzev]

The proposed solution doesn't consider how large the queue can become, app performance, UI render and convenience. I think the current approach is the standard approach used by everywhere.