View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0006502 | MMW v4 | Properties/Auto-Tools | public | 2010-09-28 01:58 | 2010-10-27 12:52 |
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 | 0006502: Ability to modify Type | ||||
Description | As discussed in 0006482, it should be possible to easily modify 'Type' in one of two ways: a) Properties dialog should include 'Type' field b) Drag and drop from one collection to another should modify Type appropriately in cases where the Collection has exactly 1 Type in its definition, this Type is assigned to the tracks. In case there are 0, 2, 3, ... Types, a dialog is shown to the user and he/she can select which Type to assign. e.g. 'This Collection contains multiple 'Types' of files. What Type do you wish to assign? (o) Type 1 ( ) Type 2 ( ) Type 3 [OK] [Cancel] | ||||
Tags | No tags attached. | ||||
Fixed in build | 1317 | ||||
|
1) Is implemented. 2) I constructed the workflow this way: If a collection is defined by only one rule and the rule consist of "Type is" then the first type is used as assignment (this works fine for the default collections) otherwise (if the collection consists of another rule(s)) the drop is not offered. Examples: For the default Audiobook collection consisting of rule: Type is [audiobook] => audiobook is used as type assignment For the default Podcast collection consisting of rule: Type is [podcast, video podcast] => podcast is used as type assignment For custom collection consisting of rules: Type is [music] Rating is >= 4.5 stars => the drop is not offered |
|
Re. 2), a single Type may often span more than one collection (e.g. Kids Music vs regular music). Would it be possible to enable this even when more than one rule is used? |
|
No, I think that the drop should not be offered for such a custom collections. See my examples above. Fixed in build 1314. |
|
Rusty have found an issue: d&d doesn't function properly when dragging between collections. e.g. drag from music to Classical Music > Bethoven --> nothing happens. |
|
Fixed in build 1315. |
|
Tested in 1315, and it's almost fixed. Now the tag is modified correctly, however, the tab doesn't refresh after the operation is completed, and so it appears to have failed. e.g. 1) drag track a to Tab:Classical Music...Beethoven 2) Switch to Tab:Classical Music...Beethoven --> track a doesn't appear! (however it does appear after pressing F5) |
|
Tabs update after D&D fixed in 1316. Assigning back to Ludek as there's a AV when droping to Entire Library node. |
|
Fixed in build 1317. |
|
Verified 1318 |