Re: DND for XEmacs 21
Jonathan Harris <jhar(a)tardis.ed.ac.uk> writes:
> | The button and modifier state is
> | ignored for file drops.
>
> Not exactly. They may have the same meaning for drop targets which are
> file containers. What does dropping a file on a dired buffer mean?
But for a filemanager dnd the target app (ie XEmacs) can't pass any
information about the state of the modifiers to the source app (ie the
filemanager), so one can't implement the usual Move/Copy semantics for
even if one wanted to. Or am I missing something.
This is a problem of the low-level protocol. If it has no ability to tell the
source of the drop if the destination has the data of such a move operation,
then the source has a problem (kill it or leave it...). This is for example a
problem of OffiX. It throws the data whereever the user releases the button,
no matter if there is someone who catchs the stuff.
Xdnd on the other hand knows if the destination can handle the drop.
Regards,
Oliver.