View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0017850 | MMW 5 | Track Browser | public | 2021-05-11 17:36 | 2021-06-25 19:31 |
| Reporter | michal | Assigned To | |||
| Priority | urgent | Severity | minor | Reproducibility | sometimes |
| Status | closed | Resolution | reopened | ||
| Product Version | 5.0.1 | ||||
| Target Version | 5.0.1 | Fixed in Version | 5.0.1 | ||
| Summary | 0017850: Auto-scroll to the selected item in Column filter after the change | ||||
| Description | We are trying to keep selection in column filter lists, after any change in column filter, where possible (just like iTunes). But it sometimes leads to the situation, where selected item is not in the visible area of the list. We should automatically scroll to the first selected item after such change. | ||||
| Additional Information | https://www.mediamonkey.com/forum/viewtopic.php?p=481310#p481310 | ||||
| Tags | No tags attached. | ||||
| Fixed in build | 2419 | ||||
|
|
Fixed in build 2403. |
|
|
1) Selecting an item in item in column 2 and unffiltering in column 1 fails 1 Select item in column 2 2 Select an item in column 1 that includes item selected in column 2 --> Selected item in column 2 is in view 3 Select All in column 1 --> Selected item in column 2 is not in view Tested with Genre > Artist > Album columns in Column Filter |
|
|
Test note - it seems, that very quick click (short time between mousedown and mouseup) is needed to reproduce. |
|
|
Fixed in the build 2418. |
|
|
Still present on 2418 for me. Tried in the Year > 2018 node set to List view with Column Filter enabled. 1 Go to 2018 node in Year 2 Select Alan Jackson in second column 3 Select Country in first column --> Alan Jackson is shown first in visible area, good! 4 Select All in first column --> Alan Jackson is no longer visible Note that after 4 I've also seen: --> Selected item in column 2 in the visible area, but at the bottom instead of top |
|
|
For me, build 2418 is worse than 2417. Now the issue crops up fairly regularly, whereas previously it was the exception rather than the rule. |
|
|
Fixed in build 2419. I cannot reproduce it with any given steps finally. |
|
|
Verified on 2419 |
