View Issue Details

IDProjectCategoryView StatusLast Update
0007494MMW v4DB/FileMonitorpublic2013-01-10 13:47
Reporterrusty Assigned To 
PriorityurgentSeveritymajorReproducibilityalways
Status assignedResolutionreopened 
Product Version4.0 
Target Version4.1.1Fixed in Version4.0 
Summary0007494: Scanning interferes with usage of the tracklist (regression)
DescriptionWhen scanning files into the library, the tracklist / filelist moves by itself, making the tracklist unusable.
TagsNo tags attached.
Fixed in build1426

Relationships

related to 0008226 assignedpetr Art & Details View: track position changes in response to activities in other dialogs 
related to 0005653 closedpetr Tracklist moves by itself whenever tracks are tagged 

Activities

petr

2011-03-10 09:43

developer   ~0023633

I've tried in MM3 and it work exactly same (tracklist will always scroll to focused node).

rusty

2011-03-10 16:19

administrator   ~0023638

The behavior that I observed was that MM was flipping to the beginning of the tracklist, but I can't figure out how to reproduce that. Closing.

rusty

2011-03-11 05:06

administrator   ~0023650

Last edited: 2011-03-21 21:46

Figured it out. It occurs when scanning if the user switches to AA View without the Column browser active.

Edit: I've also observed this to occur on occasion on Track change in the Now Playing list (i.e. New track starts playing --> position of the tracklist changes), but I cannot determine repro steps.

petr

2011-03-30 23:17

developer   ~0023983

Unable to reproduce in 1358. Retest in 1359, please.

peke

2011-04-26 23:13

developer   ~0024497

Verified No reproduce with 1367

rusty

2011-08-18 06:05

administrator   ~0027250

This issue is reproducible in 1419 and makes MM unusable during the scanning process due to:
1) The tracklist continually scrolls back to whatever track is selected (even when the user has manually scrolled to a different location)
2) If the user tries to edit a track (via F2) the edit box loses focus each time a track is scanned

petr

2011-08-23 21:31

developer   ~0027308

Fixed in 1423

rusty

2011-08-25 04:47

administrator   ~0027336

Tested 1423 and the bug still occurs in Art, Art & Details, and Details views.

Reproduce as follows:
1 Scan a drive
2 Select the first track
3 Scroll down the tracklist
--> MM will scroll back up to the selected track by itself

petr

2011-08-25 10:41

developer   ~0027341

Fixed in 1424

rusty

2011-08-31 04:46

administrator   ~0027423

This still occurs in build 1425.

petr

2011-08-31 12:55

developer   ~0027426

There was a regression in Art Browser and when Track Browser is enabled. Fixed in 1426.

rusty

2011-08-31 22:58

administrator   ~0027429

It's much better in both the Art View and A&D view, though it still jumps around periodically. I hope that can improve a bit further if possible.

The Details view is quite bad though. It continually jumps.

petr

2011-09-01 07:57

developer   ~0027430

It's jumping because new tracks are adding to the list (so it's always stay at the same position from the top of the list).

rusty

2011-09-05 20:47

administrator   ~0027457

Last edited: 2011-09-05 20:50

To clarify, the suggestion being raised is that when you have tracks
A
C
D
and only C and D are within the visible portion of the tracklist, then if track B is scanned, it would need to fit between A and C. So with the suggested approach, there would no longer be updates to the display when Album B is added (since C is the first visible item). (Unlike the current situation in which any time a track is added above the current visible location, the tracklist moves).


Another example would be with Album Art e.g. for albums:
A B C
D E F
G H I
J K L
Currently, if albums DEF,GHI are on the screen and album K1 is added, nothing happens. BUT if album B2 is added, then every entry on the screen is redrawn so that it appears as:
C D E
F G H

I would suggest that the behavior with K2 is correct, but that the behavior with B2 is not. i.e. the tracks on the screen shouldn't change because:
- There are no new albums within the currently displayed range
- The user hasn't moved (or triggered a move of) the scrollbar

Note also: on a fresh install, build 1426 _does_ repeatedly jump to the currently selected track (for the details view).

petr

2011-09-21 20:53

developer   ~0027887

There are some performance issues with this implementation i need to solve, but it need some more updates so i prefer to postpone to 4.1 (because of regression risk).