Re: [drew.adams@oracle.com: Customize value menu doesn't recognizemouse-2]

[Eli Zaretskii <eliz@gnu.org>]

> From: "Drew Adams" <drew.adams@oracle.com>
> Date: Mon, 31 Jul 2006 20:33:41 -0700
> 
>     > From: Richard Stallman <rms@gnu.org>
>     >
>     > On GNU/Linux, probably with Lucid menus, I can select from
>     > the menu using any of the three mouse buttons.
>     >
>     >      (The latter part happens only on MS-Windows.)
>     >
>     > It sounds like a bug in the way menus work in Emacs on Windows.
> 
> What Richard described for the other platforms is exactly the behavior I
> requested when I filed this bug.

I'm not sure you interpret what Richard wrote correctly: I think he
was talking about the value menu dropped when one presses on a button
inside a Customize buffer, whereas you seem to interpret that as a
more general statement about menus in general.  See below about the
latter.

> It sounds to me like the fix for the more
> annoying bug (which I also reported, I believe) was not the right fix.
> Wouldn't the right fix have been to make mouse-2 select a menu item, just
> like on GNU/Linux? That would take care of both bugs, and bring Windows into
> line with the other platforms.

Actually, what happens when you click mouse-2 in a menu on X depends
on the toolkit, AFAICS.  Xt and GTK indeed behave like you say, but
Motif behaves like MS-Windows: mouse-2 is ignored in menus, and you
need to use mouse-1.  I looked in a couple of other GUI applications
on Windows, and it looks like they ignore mouse-2 in menus.

With buttons in Customize, it's different: there all toolkits I could
try behave as Richard described, probably because Emacs itself handles
the click.

So, at least for menus in general, this doesn't sound like a behavior
aspect that is consistent across platforms.

> IOW, "Please leave things alone" ... "Done" sounds like a quick cop-out, to
> me.

Richard asked to do nothing, so I complied.

> I can't speak to hard it might be to fix this properly, so that Windows will
> DTRT, like GNU/Linux, but I can speak to what TRT would be for the user:
> exactly what Richard described.

Even though other GUI programs behave on Windows like we do now?