Welcome Guest. Please Login or Register. Apr 5th, 2018, 11:20pm
ATTENTION MEMBERS: Conforums will be closing it doors and discontinuing its service on April 15, 2018. Ad-Free has been deactivated. Outstanding Ad-Free credits will be reimbursed to respective payment methods.
If you require a dump of the post on your message board, please come to the support board and request it.
Re: WM_CONTEXTMENU oddity
« Reply #3 on: Mar 19th, 2014, 3:41pm »
SHift-F10 does nothing on either machine - I tried it, and wondered whether the keyboard EITHER has the menu button OR uses shift-F10 as an equivalent, but it sounds like it isn't as simple as that!
Trying it in my PDF viewer (since it is open...), I see that it DOES respond to both the menu key and shift-F10, in the same way (puts the context menu in the top-left of the window), and to a right-click with a context menu at the site of the mouse. That's on the desktop in Win7. On the laptop, it's a horrible full-screen, windows8-ey version which does weird things, but the same for all 3 (bars appear at the top and bottom).
Word is similar (menu key and shift-F10 pop up the menu at the cursor), but right-click gives TWO pop-up menus!
Best wishes,
D
Logged
rtr Guest
Re: WM_CONTEXTMENU oddity
« Reply #4 on: Mar 19th, 2014, 6:58pm »
That aspect of the mystery is solved - you won't see the message originating from Shift+F10 if the only window is the 'mainwin' (@hwnd%), which it is in your little test program. The reason I do see it in my application is that there's a child window (an edit control) which is evidently responding to Shift+F10 and sending the WM_CONTEXTMENU message to its parent window.
Logged