GNU bug report logs - #36269
26.2; mouse-drag-and-drop-region conflicts with mouse-avoidance

Previous Next

Package: emacs;

Reported by: Scott Otterson <scotto <at> sharpleaf.org>

Date: Mon, 17 Jun 2019 20:54:01 UTC

Severity: normal

Found in version 26.2

Done: Eli Zaretskii <eliz <at> gnu.org>

Bug is archived. No further changes may be made.

Full log


Message #11 received at 36269 <at> debbugs.gnu.org (full text, mbox):

From: martin rudalics <rudalics <at> gmx.at>
To: rswgnu <at> gmail.com, 28620 <at> debbugs.gnu.org, 36269 <at> debbugs.gnu.org,
 Scott Otterson <scotto <at> sharpleaf.org>
Subject: Re: bug#28620: Mouse drag event records wrong window for release when
 crossing frames
Date: Sat, 27 Jul 2019 11:26:47 +0200
[Message part 1 (text/plain, inline)]
> With Emacs 25.3 under MacOS 10.12, a drag with mouse-1 depressed from
> the text area of frame F1 to the text area of frame F2 improperly
> generates a drag event whose (posn-window (event-end <event>)) shows
> F1 rather than F2.
>
> Note that for a drag between frames, posn-window should return a frame
> (according to the Elisp manual but not its own doc string).  The bug is
> that the event itself records the wrong frame (the depress frame rather
> than the release frame).
>
> I have confirmed this with Emacs 25.2 under Windows 7 as well.

I tried to address this problem in the attached patch.  Tested with
GTK, Lucid, Motif and Windows builds.  Since my GNUstep Emacs is
currently broken, somebody please verify that it does something
reasonable (if anything at all) on MacOS.  Otherwise, I'd need help
from people working there.

The patch should also fix the mouse drag and drop region vs. mouse
avoidance mode problem.  Please someone verify that it does TRT now.

TIA, martin
[track-mouse.diff (text/plain, attachment)]

This bug report was last modified 4 years and 272 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.