Re: storing mouse-movement events in recent-keys and keyboard macros

[Eli Zaretskii]

> From: address@hidden (Kim F. Storm)
> Date: 07 Dec 2001 22:37:31 +0100
> 
>  {
> -  /* Don't record `help-echo' in recent_keys unless it shows some help
> -     message, and a different help than the previoiusly recorded
> -     event.  */
> +  int recorded = 0;
> +
>    if (CONSP (c) && EQ (XCAR (c), Qhelp_echo))
>      {
> +      /* Don't record `help-echo' in recent_keys unless it shows some help
> +      message, and a different help than the previoiusly recorded
> +      event.  */
>        Lisp_Object help;

Please be sure to test these changes with mouse-avoidance-mode in its
various submodes.  The special treatment of help-echo events is there
to prevent unpleasant effects when you set the mouse-avoidance-mode
to `banish', for example.

To test whether your changes didn't break that, type "M-x
mouse-avoidance-mode RET banish RET", and then move the mouse above
mouse-sensitive parts of the mode line, and see if the mouse pointer
is banished when the tooltip pops up (it shouldn't be banished).
Please also test this when the help echo is displayed in the echo
area, not in a tooltip.

Another situation where such bugs can be spotted is in the Customize
buffer: moving the mouse pointer to a button which causes help text
to pop up in a tooltip or in the echo area could cause the mouse
pointer to be banished, making it practically impossible to use
Customize.

Note that I'm not saying your changes necessarily break avoid.el--I
didn't check that.  I'm just giving you a few more tests to run, to
make sure nothing breaks.