View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0019675 | MMA | Playback | public | 2022-12-31 22:52 | 2023-02-17 04:46 |
| Reporter | peke | Assigned To | |||
| Priority | urgent | Severity | minor | Reproducibility | sometimes |
| Status | closed | Resolution | reopened | ||
| Product Version | 2.0.0 | ||||
| Target Version | 2.0.0 | Fixed in Version | 2.0.0 | ||
| Summary | 0019675: MiniPlayer: Scroll track info if it is larger than screen (regression) | ||||
| Description | Currently if playing track info is larger than screen width it does not scroll. We should make it viewable completely by scrolling. | ||||
| Additional Information | https://www.mediamonkey.com/forum/viewtopic.php?t=103290 | ||||
| Tags | No tags attached. | ||||
| Fixed in build | 1068 | ||||
|
|
This is mainly a problem in the miniplayer since it displays album art to the left and Play/Pause | Next to the right. |
|
|
Fixed in build 2.0.0.1058 |
|
|
Tested 1058 and it looks good. Re-opening for a couple of minor issues. If non-trivial, these should be pushed into a new post 2.0 bug: 1) Currently, the metadata scrolls as soon as the track appears before the user even has a chance to see the beginning! The scrolling should begin after about 1s. 2) When scrolling starts, it's a bit choppy for the first couple of seconds. Hopefully this issue is related to scrolling being initiated at the same time as a track transition and the fix to 1) will also fix this. 3) When > 1 line scrolls: a) It's difficult to read especially if the middle row isn't scrolling. It would be preferable if all 3 lines scrolled in such cases. b) it would be preferable if scrolling was 'left-justified' i.e. lines that have less text should all re-appear from the right side at the same time (otherwise it's quite difficult to read) 4) If the user presses PREVIOUS to return to the beginning of the track, the scroll should initiate again |
|
|
1), 2), and 4) fixed in build 2.0.0.1068 3) It requires a completely different (and complicated) implementation than the current ( native ) solution. |
|
|
Verified 1068. |
