View Single Post
Old 01-10-2024, 05:25 PM   #5
BetterRed
null operator (he/him)
BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.
 
Posts: 21,798
Karma: 30237628
Join Date: Mar 2012
Location: Sydney Australia
Device: none
Quote:
Originally Posted by chaley View Post
Kovid will know, but I suspect it is hard if not impossible to do. The mouse knows what field it is over so can adapt the menu. The keyboard doesn't (seem to) use the mouse position.
In my second screen shot, the dots (ants) around DOCX indicate that that's where the keyboard focus lies.

I would have thought the keyboard handler should process Shift/F10 or Menukey down/up interrupts in the same way as the mouse handler handles the right button down/up interrupts… without reference to the mouse location.

Quote:
Originally Posted by kovidgoyal View Post
well charles points out that one can avoid the click and allow pressing the context key instead, provided you are willing to move the mouse to the desired location first.
Nope - if I hover the mouse over the DOCX and press Shift/F10 I get the same 3 item context menu - Copy, Search, Re-index menu.

BR
BetterRed is offline   Reply With Quote