Do we need: A folder cannot be dropped into itself

[todd rme]

On Wed, May 30, 2012 at 7:18 PM, Elvis Stansvik <elvstone at gmail.com> wrote:
> 2012/5/28 Peter Penz <peter.penz19 at gmail.com>:
>> On 05/28/2012 09:47 PM, Alex Fiestas wrote:
>>>
>>> On Monday, May 28, 2012 09:32:43 PM Peter Penz wrote:
>>>>
>>>> On 05/28/2012 08:44 PM, Alex Fiestas wrote:
>>
>> [...]
>>
>>>> Sorry, I but did not understand your suggestion: If the users drops
>>>> folder A into A - what should be done here instead of showing the
>>>> error-message?
>>>
>>> Nothing, the folder will still be selected and nothing should happen.
>>
>>
>> OK.
>>
>>
>>>>  >  Maybe in that case we could
>>>>  >  move everything into the folder besides the error?
>>>>
>>>> But folder A contains already everything - what should be moved?
>>>
>>> If we have selected folder A and files B C, then we drop A,B,C into A
>>> files B
>>> and C should be moved into A.
>>
>>
>> OK, I understand now. But I'm not really sure if just copying B and C
>> without any feedback should be done. We assume here that the user
>> accidentally selected folder A, but it might also possible that the user
>> accidentally has hovered the wrong folder when dropping.
>
> Right, and at least for my part I would say that I more often drop in
> the wrong place than select the wrong folder.

On the other hand I am the opposite, at least when moving folders onto
folders.  Having a better way of handling this could also make the
work flow "create new folder -> move all existing files and/or folder
into that folder" much easier.  That is why I suggest having a
"cancel/skip" dialog box, it lets you continue with the transfer if
you did it intentionally or end it if you didn't, which can speed up
certain workflows.

-Todd