Quote:
Originally Posted by BetterRed
As far as I'm concerned the menu key (which I use where ever possible) always works exactly the same as a right mouse button click. Elsewhere in calibre, eg the book list, metadata editor, comments editor, the tag browser etc. And in windows, my file manager, imaging editing tools, text editor etc. And in Sigil's code view window after F4 (Next spelling error), and Notepad++'s editing window after Alt/N (Next spelling error).
The only instance I can think of where it doesn't work like a right button mouse click is after F8 (Next spelling error) in the calibre-editor code view window.
|
I see it is changed now
.
Yes, perhaps my "It does not as a matter of course mimic the mouse right click context menu so its behaviour may be different" was a bit short.
What I was alluding to is the context menu that appears is dependant on the message or call that is used (in the Windows API case) so they are not naturally going to be the same. It was just a remark and was not a judgement as to what was correct or most desirable (although the Windows GUI recommendation is that they be the same, though I only think that is so because I am no programmer). Nor was I judging nor lobbying as to how it should work in Editor as because of my approach it is irrelevant to me.
On checking, under the F8 circumstance that you outlined in Editor, I see that SHIFT-F10 does not bring up an extended context menu either. So Windows keyboard maestros may find that a bit of an inconvenience too.
Regarding the practice in other programs, I have checked and I do have some other non Windows GUI applications where the mouse and Application/Menu key context menus are different, and even at least one that the context menus do not exist in either case at all (that one being the OED Dictionary). However, I think for most, if not all, Windows GUI applications I regularly use (Office Suite, etc., etc., etc.) the context menus are probably the same for both mouse and key.
John