View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0017343 | MMW 5 | Main Panel | public | 2021-01-07 18:07 | 2021-05-27 20:15 |
| Reporter | lowlander | Assigned To | |||
| Priority | urgent | Severity | major | Reproducibility | random |
| Status | closed | Resolution | reopened | ||
| Product Version | 5.0 | ||||
| Target Version | 5.0.1 | Fixed in Version | 5.0.1 | ||
| Summary | 0017343: Switching Next in Properties can move selection in Media Tree up one node | ||||
| Description | I can't guarantee that the Next in Properties caused it, but it did happen several times on Next action that the Media Tree selection went 1 node up (next node above selected node, not parent). However the Media Tree selection also changed while typing this (MM was playing and finishing Volume Analyzing of just edited Album). | ||||
| Tags | No tags attached. | ||||
| Fixed in build | 2408 | ||||
|
|
Based on the logs you tested 2291, but this has been already fixed in 2292 as 0016991 i.e. sounds like the " Barrys issue with MM5 reacting to keystrokes even when not focused", see 0016991:0061110 So please re-test in 2292 and if you are unable to replicate in 2292 then just close this case as verified |
|
|
Verified 2293 No issues, 2291 observe issue as described. |
|
|
Just Re verified 2295 Same behavior as in 2293. Closing |
|
|
Seeing this again on 2299, it may require MediaMonkey to be running a while. It seems that either Analyze Volume or the editing of Properties in Properties of a playing file from the Playing window caused it. Logs and Screencast in the same place |
|
|
Assigned back to me, as it seems to be identical to 0016787 Based on the logs subsequent folder auto-update (after any track property change) - be it via properties or e.g. by changing play count during playback somehow causes this issue. |
|
|
I haven't been able to replicate (tested with your database on Pinned > TempMusic folder subnodes -- like in your screencast), but based on code revision and debug log analyzing I (hopefully) fixed the issue. I also added more debug messages for the future. |
|
|
Unable to reproduce on 2408 |
