View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0017573 | MMW 5 | Conversion/Leveling | public | 2021-02-17 17:14 | 2022-04-29 22:57 |
| Reporter | rusty | Assigned To | |||
| Priority | urgent | Severity | minor | Reproducibility | always |
| Status | closed | Resolution | fixed | ||
| Product Version | 5.0 | ||||
| Target Version | 5.0.3 | Fixed in Version | 5.0.3 | ||
| Summary | 0017573: Volume analysis error flow is confusing | ||||
| Description | When the user: 1 initiates volume analysis for a track that can't be analysed -->Timed Error dialog appears for the track that can't be analyzed: There was a problem analyzing volume for the following tracks: ....list of tracks.... [Continue] [Cancel] 2 Press [Cancel] (or [Continue] if only a single track is being analyzed) --> Summary dialog appears that's near identical to the previous one: There was a problem analyzing volume for the following tracks: Retry [ ] Track 1 [ ] Track 2 .... [OK] see: https://www.screencast.com/t/TLtOzp7o4 The summary dialog is fine, but a more appropriate approach for the timed error dialog would be to use a Toast message each time an error occurs (as long as the toast stays in one place and doesn't flash multiple-toast messages). e.g. Using existing strings: Error: Volume analysis (<FileName>). <Problem description>. . . . . . . . . . . . . . . . . . . [Cancel] With new strings: <FileName>: There was a problem analyzing volume. <Problem description> [Cancel] Note: there's no need for a 'Continue' button with a timed dialog or a toast since that's the default behavior. | ||||
| Tags | No tags attached. | ||||
| Fixed in build | 2617 | ||||
|
|
Moving to 5.1 as it requires new strings and if we want to go this way (to change the timed error dialog to toast) then we should probably unify with all the others possible "timed error dialogs" i.e. be it analyzing, volume leveling, ripping, file conversion, downloading, scanning, organizing ... |
|
|
As proposed at 17904, we can use existing strings for the toast. <CommandName> (error): <file> [Cancel...] Note: I haven't reviewed the usecases of ripping, file conversion, downloading, scanning, organizing, etc. But yes, if other 'timed error dialogs' are duplicated with Summary dialogs, then we can probably use the same approach. Each of those usecases should be tested and a new bug created. But I suggest resolving the volume analysis 0017573 and volume 0017904 leveling issues for now. BUT only if user interaction with the toast message isn't blocked by the high CPU utilization associated with the operation. |
|
|
Fixed in 2617. i.e. only the Summary dialog appears now and the duplicated "timed dialog" with Continue button no longer appears. As for the need for a toast: Personally I don't think that the toast message is actually needed, it would be annoying anyhow IMO and probably user would fail to read it anyway (as the text would blink when there are many files in a row having trouble with the operation), so showing just the Summary of the operation with the list of failures is fine IMO. |
|
|
Verified while testing 0017904 on build 2618. And yes, the current workflow seems to be fine without the toast messages. |
