[Xquartz-dev] 2.3.1_beta1

[Martin Costabel]

xquartz-dev.5.mzs at spamgourmet.com wrote:
[]
> The other thing is that I could have sworn that the emulate three button 
> mouse used to use option and command. It now seems to use ctrl and option. 
> This makes it so that you can't do the menus in xterm. I have not had to 
> use a one button mouse is a really long time but I swear it used to work 
> that way. I wonder if I can work around i with xmodmap?

I don't see any difference with 2.3.0 here: The buttons 2 and 3 are 
still activated by pressing opt and cmd before clicking. The fact that 
the xterm menus don't work except for the "Main Options" menu is also 
old. I filed a bug for it long ago, but it was immediately closed as 
invalid. Well, it's still valid, but since I rarely use those xterm 
menus or even xterm, I won't insist. I would quote the bug ticket #, but 
I can't look at it right now on the macosforge wiki, because clicking on 
"All reports,... including closed" does not show these reports, but an 
error message

"Report execution failed: column "modified" does not exist LINE 16: 
(CASE status WHEN 'closed' THEN modified ELSE (-1)*p... ^"

The 3 xterm menus are obtained via ctrl-button1 (= ctrl-click, this 
still works), ctrl-button2 (= ctrl-opt-click, doesn't work), and 
xtrl-button3 (= ctrl-cmd-click, doesn't work).

The reason that the latter two don't work is probably that, as has been 
reported here on this list (also bug Ticket #143, marked as Milestone: 
2.3.1, but still present in the latest beta), opt-click and cmd-click 
give ButtonPress events immediately followed by ButtonRelease events, 
before the button is released. The subsequent release of the button does 
not generate any event. So it is likely that the menus are indeed 
dropped down, but only for a microsecond or so, and you don't see them.

-- 
Martin