autoresume: Manual: Clarify precedence rules for resume positions
Resume positions stored in bookmarks take precedence over autoresume. Technically, the resume position for the "Resume Playback" function (which is also saved across power-off/power-on) also takes precedence over autoresume. However, there is no way for a user to tell as it is identical to the autoresume position for the last-played track, so don't highlight it in the manual. git-svn-id: svn://svn.rockbox.org/rockbox/trunk@29548 a1c6a512-1295-4272-9138-f99709370657
This commit is contained in:
parent
bd05c07584
commit
04043fd3ae
1 changed files with 4 additions and 2 deletions
|
@ -9,8 +9,10 @@ database has been initialized.
|
||||||
When automatic resume is enabled, manually selected tracks resume
|
When automatic resume is enabled, manually selected tracks resume
|
||||||
playback at their last playback position. It does not matter in which
|
playback at their last playback position. It does not matter in which
|
||||||
way you start the track; tracks are resumed whether they are navigated
|
way you start the track; tracks are resumed whether they are navigated
|
||||||
to through the database browser or file browser, from a playlist or
|
to through the database browser or file browser, by starting a
|
||||||
bookmark, or by skipping through tracks in a playlist.
|
playlist, or by skipping through tracks in the current playlist. (As
|
||||||
|
an exception, when a track is resumed by loading a bookmark, the
|
||||||
|
playback position saved in the bookmark takes precedence.)
|
||||||
|
|
||||||
Optionally, you can also enable automatic resume for automatic track
|
Optionally, you can also enable automatic resume for automatic track
|
||||||
transitions. In this case, the next track will be resumed as well
|
transitions. In this case, the next track will be resumed as well
|
||||||
|
|
Loading…
Reference in a new issue