View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0012221 | MMW v4 | DB/FileMonitor | public | 2014-10-06 18:44 | 2014-10-16 01:05 |
| Reporter | peke | Assigned To | |||
| Priority | immediate | Severity | major | Reproducibility | always |
| Status | closed | Resolution | fixed | ||
| Product Version | 4.1.5 | ||||
| Target Version | 4.1.5 | Fixed in Version | 4.1.5 | ||
| Summary | 0012221: Removing tree node in one collection removes all tracks in all other collections | ||||
| Description | For example, in order to remove all video files from tree node and and subnodes right click on tree node and remove it, all tracks from Music Collecting is also also removed if they are contained in that same path/node. Desired behavior would be to remove node and all tracks of Root node criteria not all tracks. | ||||
| Tags | No tags attached. | ||||
| Attached Files | |||||
| Fixed in build | 1718 | ||||
|
|
Peke, I don't see any remove option in the right-click menu of the Video collection node, could you better specify the steps to replicate this issue? |
|
|
I uploaded Image with Following steps that will delete Music folder from Collection Music also even remove is related to Tracks only in Video Collection and should be limited to those tracks. |
|
|
Ok, it has always worked like this in case of folder removing. In that case the following dialog appears before folder removing: Are you sure that you want to delete C:\Music\ ? (_) Delete Library content from Library only (o) Delete Library content from Library and Computer (_) Delete all content from Library and Computer Which implies that at least the third option really should delete _all_ folder content. Actually I see other usability issues if we would change the old standing behaviour now. The default 'Entire Library' is disabled by default and user might not realize how to delete all library content from the folder. @Rusty, do you think that this needs a change for 4.1.5 ? |
|
|
There's definitely a usability issue, but it's debatable whether it's a showstopper. When the user attempts to rename a folder, it's clear that it applies to _all_ content. But when the user attempts to delete a library folder via the location node, it's unclear whether it applies to all collections or not; - a user should logically expect that it only applies to the content contained within the current collection if the user selects (Delete Library content from the Library only OR Delete Library content from Library and Computer) - HOWEVER, delete 'C:\Music' implies that the directory is being deleted, which does constitute a clear warning that it's the actual directory that's being deleted rather than the content represented by that directory node. As to the usability issue pointed out by Ludek, I don't think that's a serious issue--if users want to delete _all_ content, then they can do so by deleting from each collection. Summary: I think that this issue should be fixed, though we can defer it if there's too much risk associated. I wonder though if there's a reason why it was implemented in this fashion in the first place--it seems strange that we would have overlooked such a usability issue... |
|
|
I agree mostly. Here is logical behavior of Selection and MMW proposed options: (x) Delete Library content from Library only -> Delete Only library content for that collection (_) Delete Library content from Library and Computer -> Delete Content from Library and Files From that collection (_) Delete all content from Library and Computer -> Delete Library and files from all collections (Additional Line in red would be shown informing users that this action is not reversible and it will delete not just all from current collection but from all other collections Summary: We have not reviewed this functionality after MMW 3.x where we changed Library filters to Collections. When we used filters and when "Entire Library" was only node and all actions were actually done on whole MMW library. This should not be hard to fix as it should only change SQLite queries to add additional condition where collection is looked at instead of Entire Library, also it should not be high risk fix. |
|
|
Addition: Note that Auto Organize and all other MMW functions are collection based so remove should be consistent to that. |
|
|
Fixed in build 1718. |
|
|
Verified 1718 |
