[chandler-users] [d/f] Deleting collections only vs. collections and items

[Reid Ellis]

Hi Andre,

I think the issues is that since the items are not in any collection  
(not even the Dashboard), there will be no way to access them once  
the collection they are in is gone.

However, there does seem to be a bug, since if you add an item in  
your not-in-Dashboard collection to another collection, that item  
will remain after you delete the not-in-Dashboard collection, despite  
the warning dialog. The dialog should be checking for items in other  
collections and changing the wording, perhaps to "Deleting <x> will  
move some items that are only in <x> to the Trash".

I've filed Bug 9511:
	https://bugzilla.osafoundation.org/show_bug.cgi?id=9511

Feel free to add any more comments to that bug.

Reid

On Jun 13, 2007, at 12:44, Andre Mueninghoff wrote:

> Hi Everyone,
>
> A "feature or bug" type question...I have noticed (using r14690)  
> that if I have a collection be not included in the Dashboard, that  
> when I select collection-delete, I am prompted with the warning  
> that deleting the collection will move its items to the Trash. If I  
> next include the same collection in the Dashboard, then when I  
> select collection-delete, I am prompted to choose between deleting  
> the collection only or the collection and its items. I was  
> expecting this choice between collection only and collection and  
> items in all cases. Is it a feature or other technical necessity to  
> have a collection be handled differently with respect to deletion  
> based upon whether or not the collection is included in the Dashboard?
>
> Thanks, Andre