GNU bug report logs - #28620
Mouse drag event records wrong window for release when crossing frames

Previous Next

Package: emacs;

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


View this message in rfc822 format

From: Robert Weiner <rsw <at> gnu.org>
To: Alan Third <alan <at> idiocy.org>
Cc: 28620 <at> debbugs.gnu.org
Subject: bug#28620: Interact directly on Emacs bug#28620: mouse drag event records wrong release window
Date: Wed, 4 Oct 2017 16:07:56 -0400
[Message part 1 (text/plain, inline)]
On Wed, Oct 4, 2017 at 2:59 PM, Alan Third <alan <at> idiocy.org> wrote:

>
> It looks like there’s maybe a neater way to get the current frame
> under the mouse...
>
>     Lisp_Object frame = Qnil;
>     NSWindow *w = [NSApp windowWithWindowNumber:
>                          [NSWindow windowNumberAtPoint:[NSEvent
> mouseLocation]
>                            belowWindowWithWindowNumber:0]];
>     if (w != nil)
>       XSETFRAME (frame, ((EmacsView *)[w delegate])->emacsframe);
>
>
The ​mouseDown​ function (called by the various mouseUp functions) uses
`emacsframe' to set the appropriate frame.
How does the above modify emacsframe?  Doesn't XSETFRAME just set the value
of the local `frame'?

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.