RE: [drew.adams@oracle.com: Customizevaluemenudoesn'trecognizemouse-2]

["Drew Adams" <drew.adams@oracle.com>]

    Because on the menu bar, mouse-2 doesn't activate the menu on
    MS-Windows (and with some X toolkits, such as Motif).

So, let the inconsistency appear there, where it won't hurt: If mouse-2
cannot open the menu-bar menu, then there is no harm in letting mouse-2
choose an item from the menu (if opened by mouse-1).

In that case, the inconsistency 1) allows more functionality, not less, and
2) will not arise, in practice, because the inability occurs in the
initiating action, _opening_ the menu, not in the followup action, choosing
from it.

IOW, it is better to 1) have mouse-2 be unable to open the (menu-bar) menu
(even if it lets you select from it, once opened) than to 2) let mouse-2
open the (Customize value) menu but then not let you select from it. Users
will fall into a trap with #2, but not with #1.