GNU bug report logs -
#36269
26.2; mouse-drag-and-drop-region conflicts with mouse-avoidance
Previous Next
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
View this message in rfc822 format
> From: martin rudalics <rudalics <at> gmx.at>
> Date: Sat, 27 Jul 2019 11:26:47 +0200
>
> 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.
Thanks, a few minor comments below.
> + /* If forced to complete the update, no input is pending or we are
> + tracking the mouse do the update. */
Commas missing here. Should be
/* If forced to complete the update, no input is pending, or we are
tracking the mouse, do the update. */
> - /* If this event is on a different frame, return a switch-frame this
> - time, and leave the event in the queue for next time. */
> + /* If this event is on a different frame, return a
> + switch-frame this time and leave the event in the queue
A comma missing before "and".
> @@ -3995,7 +3992,7 @@ kbd_buffer_get_event (KBOARD **kbp,
> }
> }
> /* Try generating a mouse motion event. */
> - else if (!NILP (do_mouse_tracking) && some_mouse_moved ())
> + else if (some_mouse_moved ())
Can't we have mouse motion events outside track-mouse?
> + DEFVAR_LISP ("track-mouse", track_mouse,
> + doc: /* Non-nil means generate motion events for mouse motion.
> +The sepecial values 'dragging' and 'dropping' assert that the moue
^^^^^^^^ ^^^^
Typos.
Also, the quoting in doc strings should be `like this'.
> + /* While dropping use the last mouse frame only if there is no
> + currently focused frame. */
A comma missing before "use".
There's too much of whitespace changes in the rest of the patch,
making it very hard to review. Can you show the patch without
whitespace differences?
Thanks.
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.