GNU bug report logs -
#28620
Mouse drag event records wrong window for release when crossing frames
Previous Next
Reported by: rswgnu <at> gmail.com
Date: Wed, 27 Sep 2017 15:45:01 UTC
Severity: normal
Done: Eli Zaretskii <eliz <at> gnu.org>
Bug is archived. No further changes may be made.
Full log
Message #98 received at 28620 <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/plain, inline)]
On Tue, Oct 17, 2017 at 4:57 AM, martin rudalics <rudalics <at> gmx.at> wrote:
> > Yes, you would need to follow a common drag-and-drop protocol.
> > I don't understand why that is an issue if that is what you want
> > to do.
>
> Wasn't that something _you_ wanted to do? If not then we can obviously
> ignore it.
Yes, I would like Emacs drag-and-drop to work across Emacs frames and
potentially even across other applications using whatever protocol is
common to the platform in use.
>
> >> At least for top-level windows. This will work as long a child windows
> >> are fully contained by their parents which IIUC is not necessarily true
> >>
> f
> or macOS systems.
> >
> > Could you give a concrete example of where this might be a problem
> > so I could test code against it?
>
> Hardly. Child windows are a separate problem because, for example, on X
> you currently cannot drop files on them - the drop goes to the parent
> window instead.
We would certainly live within the constraints of the drag-and-drop
protocol.
>
>
> >>> and (2) a function would be needed to get the attributes of
> >> those windows.
> >
> > I have figured that part out from the macOS APIs.
>
> Window attributes are a problem on X. You will learn about that as soon
> as you try to adapt your code for it.
Ok. It would be more helpful if you explained which problems you feel are
relevant to the discussion at hand.
Bob
[Message part 2 (text/html, inline)]
This bug report was last modified 4 years and 333 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.