swick@ATHENA.MIT.EDU (Ralph R. Swick) (09/08/89)
> Ctrl ~Meta <Btn2Down>: mode-menu()\n\ > and > ~Meta <Btn2Up>: insert-selection(PRIMARY,CUT_BUFFER0)\n\ > which I interpret to mean, "If you have Control but not Meta pressed and > you push button 2 down, pop up the appropriate menu," and "whether or not > you have Control down, as long as you don't have Meta down, paste the cut > buffer on button 2 release". > > (1) Have I correctly interpreted these lines? yes. > (2) Is this a bug? stylistically, yes. In fact, it wasn't a problem in the R3 implementation as the mode-menu action grabbed the pointer, causing the ButtonRelease event went to go to a different window. > (3) Fixed in R4...? Probably (:-). Chris Peterson has a spiffy new menu widget for Xaw and we'll probably find that this lurking inconsistency will bite people in the future. I can't explain why you're being bitten now.
PJS@GROUCH.JPL.NASA.GOV (Peter Scott) (09/08/89)
Just observed what seems to this writer to be unsociable behavior in XTerm and wanted to check out my analysis. I noticed that on pressing Control + button 2 down, a menu popped up, as desired. However, on releasing button 2, the cut buffer was pasted in the window, which appears to make little sense if I want to pop up the menu without trashing my window. I looked in the FM and found under "KEY/BUTTON BINDINGS" the lines Ctrl ~Meta <Btn2Down>: mode-menu()\n\ and ~Meta <Btn2Up>: insert-selection(PRIMARY,CUT_BUFFER0)\n\ which I interpret to mean, "If you have Control but not Meta pressed and you push button 2 down, pop up the appropriate menu," and "whether or not you have Control down, as long as you don't have Meta down, paste the cut buffer on button 2 release". (1) Have I correctly interpreted these lines? (2) Is this a bug? I have not seen it mentioned here. Obviously I can change the translation table myself but why was this bizarre choice made in the first place? (3) Fixed in R4...? Peter Scott (pjs@grouch.jpl.nasa.gov)