View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0017641 | MMW 5 | Now Playing | public | 2021-03-09 02:05 | 2022-05-06 10:54 |
| Reporter | rusty | Assigned To | |||
| Priority | high | Severity | minor | Reproducibility | always |
| Status | closed | Resolution | fixed | ||
| Product Version | 5.0 | ||||
| Target Version | 5.0.3 | Fixed in Version | 5.0.3 | ||
| Summary | 0017641: Initiating playback doesn't trigger playing to scroll to the playing track | ||||
| Description | If the user isn't selecting/editing within the Playing list, then clicking PREVIOUS/NEXT causes it to auto-scroll to the playing track. This doesn't work correctly if the user presses PLAY to initiate playback that has been stopped if the playing list isn't positioned at the currently playing track. e.g. 1 Run MM, double-click a track --> Playing list auto-scrolls to the position of the playing track and continues to do so as each new track starts playing (if the user isn't actively selecting/editing a track in NP) 2 Stop playback 3 Scroll through the Playing list 4 Click the PLAY button --> The correct track starts playing, but the Playing list doesn't auto-scroll to it in the Playing list! Clarification: the suggested change is that STOP-->PLAY should initiate auto-scroll (Pause-->Play shouldn't, as is currently the case). Note: this isn't critical since the issue corrects itself i.e. as soon as the next track starts playing, the Playing list auto-scrolls to the correct position | ||||
| Tags | No tags attached. | ||||
| Fixed in build | 2621 | ||||
|
|
In addition, when switching to a different NP view, the list doesn't show the playing track. e.g. 1 Switch from Music > Artists to Playing > List --> the List view displays from the top (instead of centered around the currently playing track)! 2 For the Playing element, switch from Simplified list to List (or vice versa) --> the list displays from the top (instead of centered around the currently playing track)! Michal indicated that this could conflict with current Listview restoration logic. This is a really minor case since it only occurs on config changes so it can probably be deferred indefinitely. |
|
|
Fixed in build 2621. Tried also the situations from comment, seems to be working ok. |
|
|
Verified 2621 All description cases and those from 0017641:0062316 work OK. |
