View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0008567 | MMW v4 | Other | public | 2011-10-26 21:52 | 2011-11-09 00:14 |
| Reporter | Ludek | Assigned To | |||
| Priority | urgent | Severity | minor | Reproducibility | always |
| Status | closed | Resolution | fixed | ||
| Target Version | 4.0 | Fixed in Version | 4.0 | ||
| Summary | 0008567: Duplicate Content: hash calculation can't be triggered in some cases | ||||
| Description | If one go to Music -> Files to edit -> Duplicate Content and expand the node then MediaMonkey shows this dialog: 2256 tracks in your library have not been analyzed for redundancy. Would you like to analyze them now (this takes a fair amount of time)? [] Don't show this again => if one checked the '[x] Don't show this again' checkbox and terminates the calculation task or simply close MM then he is never asked again to calculate the signatures (as expected), but there is no way to start the calculation again! I think that in such a situation MM should automatically start the claculation thread on background when the 'Duplicate Content' node is expanded. | ||||
| Tags | No tags attached. | ||||
| Fixed in build | 1450 | ||||
|
|
Agreed. Assuming that you mean that it should start the calculation thread if the user has indicated both 'Yes' AND '[x] don't ask again' AND has clicked the node. |
|
|
Fixed in build 1450. Note that I added a prevention from starting more than one hash calculation thread at once. And I also changed the behaviour so that node is expanded even if the calculation starts. In previous builds the node failed to expand entirely when calculation started. |
|
|
@Rusty: No I meant that it should start the calculation thread if the user has checked '[x] Don't show this again' and expands the node. It doesn't depend on the previous results of 'Yes'/'No' in the dialog. Otherwise there would be no way to start the calculation again. Because this 'Don't show this again' is missing from 'Options->General->Confirmations |
|
|
Re-resolving. The current implementation is fine. |
|
|
Closing |
