Re: Drag and drop patch for X, please review.

[Jan D.]

> I think it is better not to try to say yes and no in different Emacs
> buffers.  We should treat all of the buffer text areas in a uniform way
> as regards accepting drops there.

Okay, then we can put the data in the kill ring if it can't be inserted.

> However, the menu bars could be treated differently, since the C code
> can tell whether the pointer is in a menu bar.  Likewise, maybe Emacs
> could always reject drops in scroll bars, or in the echo area when the
> minibuffer is inactive (or maybe always in the echo area).  The C code
> can tell if a window is a minibuffer window and whether it is active.
>
> Mode lines also would have to be treated uniformly, I guess.
> Is there a useful meaning for a drop in the mode line?

Well, if a drop of a file opens the file, it should do it for the
mode line also I think.

> Different buffers can still handle the same kind of drop in different
> ways, based on local key bindings.  There's no need to look thus up
> except at the end, in response to the event.

The current drag and drop event from C to Lisp is not intended to be
anything but internal, i.e. to be able to implement the protocol in 
lisp.
I guess I could create an additional event for the final drop, but
information must be extraced before the final event (see other mails).

> If we want dropping a file into the menu bar to open the file, then I
> suggest it open the file using find-file-other-window.  While no
> method is always best, that's the way users most often prefer.

That is easy to do.

        Jan D.