View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0007538 | MMW v4 | Other | public | 2011-03-17 17:18 | 2011-04-26 23:11 |
| Reporter | rusty | Assigned To | |||
| Priority | urgent | Severity | minor | Reproducibility | always |
| Status | closed | Resolution | fixed | ||
| Product Version | 4.0 | ||||
| Target Version | 4.0 | Fixed in Version | 4.0 | ||
| Summary | 0007538: Thumbnail generation status bar is 'jumpy' | ||||
| Description | The thumbnail generation status bar is confusing during the scans in MM4--it opens/closes repeatedly during the scanning process, each time indicating that is is scanning tracks that have already been scanned. e.g. 1) It opens indicating generating thumbnails for tracks x of 50, and then closes 2) It opens again indicating that it is generating thumbnails for tracks x of 100, quickly scans through 1-50 that have already been generated, and then more slowly for tracks 50-100 and then closes 3) It opens again indicating that it is generating thumbnails for tracks x of 200, quickly scans through 1-100 that have already been generated, and then more slowly for tracks 100-200 and then closes This behavior (steps 2 and 3) continues until the scanning process is complete. MM shouldn't present such a jumpy UI to the user. The suggestion was proposed to simply get rid of the thumbnail status bar, but rejected, because the user should see why the cpu is being used by MM. The best suggestion for the short term is to not display the Thumbnail generation status bar while a scan is in progress, but to display it any time a scan isn't in progress. side note: isn't it wasteful of cpu cycles to begin the thumbnail generation process anew when a scan is in progress (i.e. if MM knows that tracks 1-50 already have thumbnails, why should it attempt to generate them again)? | ||||
| Tags | No tags attached. | ||||
| Fixed in build | 1356 | ||||
|
|
Note: When thumbnails are being generated, the scanning process slows down by an order of magnitude (this may be related to the fact that my files are stored on the network). If there's no indication of the reason for the slowdown, users will think MM is buggy. Two points: a) Instead of not displaying the thumbnail status bar during the scanning process, it might be preferable to simply display it without having the process restart over and over during any one scan. b) Alternatively to a) or in conjunction, is there a possibility of optimizing performance so that thumbnail generation speed has no impact on scanning speed? |
|
|
Fixed in 1356 |
|
|
Verified 1367 |
