summaryrefslogtreecommitdiff
path: root/apps/lang/italiano.lang
diff options
context:
space:
mode:
authorChristian Soffke <christian.soffke@gmail.com>2024-09-29 17:42:03 +0200
committerChristian Soffke <christian.soffke@gmail.com>2024-10-26 11:28:01 -0400
commit7592d2ca5eab2e684f45b7a7163f1594f3c36c96 (patch)
treecee9b60519d66649f65369c8a842596a63b6b944 /apps/lang/italiano.lang
parentcb1346b640017a821105e8d8b4cc51640858c8d1 (diff)
downloadrockbox-7592d2ca5eab2e684f45b7a7163f1594f3c36c96.tar.gz
rockbox-7592d2ca5eab2e684f45b7a7163f1594f3c36c96.zip
playlist: deprecate PLAYLIST_COMMAND_CLEAR
In the following scenario, a garbage file name would be written to the control file for the playing track (resulting in a failure to resume correctly): - "Keep Current Track When Replacing Playlist" option is set - A track is playing that was not inserted but instead comes from a playlist file on disk - User performs "Playing Next..." -> "Play" on some tracks, so that the current playlist is replaced (but leaving the playing track queued) - User saves the playlist while queued track is still playing (the offer to remove queued tracks is declined) The failure occurs because the pl_save_update_control function assumes that the seek offset for queued files always points into the control file. Meanwhile, the remove_all_tracks_unlocked function adds the PLAYLIST_QUEUED flag indiscriminately, even if a track comes from a playlist file instead of having been inserted. Theoretically, this could be addressed by adding the playing track's file name as a parameter to PLAYLIST_COMMAND_CLEAR, which the track is then updated to point to, unless it was already inserted (alternatively, we could seek within the playlist file for such tracks). Unless I'm missing something, it may be preferable, though, to get rid of PLAYLIST_COMMAND_CLEAR completely, and instead have the remove_all_tracks_unlocked function start over with a fresh control file, into which we insert a single ('P' and) 'Q' command. This seems to have several advantages: - When resuming, we eliminate the need to parse and handle all of the outdated entries again that end up being cleared anyway - It is ensured that the control file doesn't rely on the existence of a playlist file anymore after the playlist has been cleared - We can reset the playlist's file name, which should make it less likely for the user to overwrite their previous (now unconnected) playlist that was still displayed in the Save dialog - Unrelated bookmarks for the previous playlist aren't displayed anymore - Improved consistency with existing behavior when the "Keep Current Track When Replacing Playlist" was disabled. Change-Id: I41a89295bbac878807d65db9cf67b8a485daf0e5
Diffstat (limited to 'apps/lang/italiano.lang')
0 files changed, 0 insertions, 0 deletions