View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0003434 | MMW v4 | Properties/Auto-Tools | public | 2007-08-26 11:23 | 2007-08-27 19:13 |
| Reporter | jiri | Assigned To | |||
| Priority | immediate | Severity | minor | Reproducibility | always |
| Status | closed | Resolution | fixed | ||
| Product Version | 3.0 | ||||
| Fixed in Version | 3.0 | ||||
| Summary | 0003434: Improvements of Playlists in Properties dialog | ||||
| Description | Playlists window in Properties dialog is certainly useful, I'd just say that there can be some things a little confusing: 1. Checkboxes are just next to Playlists, not Auto-Playlists. It's clear why tracks can't be removed from Auto-Playlists, I just wonder whether we could better communicate this by showing a ticked checkbox there, but in disabled state, so that user would know that it can't be un-ticked? 2. It might be slighly unclear that user must untick checkbox and then press Ok button to remove a track from given Playlist. What about adding a button below the list titled like 'Remove track from unticked Playlists'? | ||||
| Tags | No tags attached. | ||||
| Fixed in build | 1066 | ||||
|
|
Assigning to Rusty with Immediate priority in order to decide whether to implement this in 3.0. |
|
|
1. I agree with you. 2. I think that the current implementation is better. That's how the entire Properties dialog works (i.e. everything is committed when the user presses ok) and I think it would be more confusing to implement something different here. |
|
|
Assigning to Ludek to implement 1 & 3. Notes: 1. vsDisabled VT state should be probably used for these nodes. 2. Ok, generally speaking I agree, I just wonder whether some explanation text or something like that wouldn't make it clearer. However, it doesn't seem to be really important... 3. Playlists aren't sorted, Playlists are first and Auto-Playlists then. |
|
|
Fixed in build 1066. |
|
|
Verified 1066. |
