on 06/26/02 23:12, ned at bike-nomad.com wrote:

> How should this work? It's possible that some objects in the selection
> resist deletion.

I think this should work just trashing them all.  Because we can drop an
object into the TrashCan even if its resist deletion option is on.

In consideration of the current specification, it seems that the "resist
being deleted" option is not working properly as we suppose.

For example, when resist deletion objects were preserved in the trash, we
could delete them easily without any confirmation.  If a morph has resist
deletion submorphs, we can delete the owner not only dropping into a
TrashCan but also clicking pink halo without any confirmation, too.

So, I think it is not the time to care the inadequate resist deletion option
for fixing the problem before official 3.2 release.

> I suspect what should be done is to simulate a drop event for each of
> the selected items, and remove those that got dropped successfully
> from the selection. If all were dropped successfully, it would delete
> itself.

It's nice idea if the "resist being deleted" option was available even if a
drop-into-TrashCan event.

> This would leave those objects that resisted being dropped on
> the receiver (in this case the TrashCan) in the selection.

I prefer they will return their original place before they are moved.

-- 
Masato Sumi