Somehow, I would like to programmatically Select, Dropdown, Highlight, and Click a menu item in the top of my "Dialog/Window" (Not a "Popup" which I believe is more commonly what happens when you "Right-Click" and a menu "pops-up")
I could have sworn I asked this before, but searching I may not have, but I did find some similar quests with some interesting ideas including what may be most promising is tracking the "WM_MENUSELECT" and then replicate it (which I figured would be something like
where "1" was my 1st attempt just to see if I could click a menu (anyyyyy menu) item which failed miserably, so I got to go back and read again and figure it out.
Anyways, I am sure it MUST have been asked and answered before, and I am just not searching the correct terms to find an example.
Eventually, I would like to write a routine that if running a tutorial, or a demo of the product, that I could actually show where the menu item is located (vs what currently I have to say stuff like "Tools--->Troubleshooting--->I have a problem with _______" instead of showing where the menu item is that could have a tool to solve your problem)
"Eventually" may be a ways off, but I figure if I can take "Baby Steps" showing the user why something opened rather than just calling the function that opens the tool, it could go a long way towards easing the users experience until the time I can take the time and "Hand-Hold" or "Walk-Thru" each step with each user
I could have sworn I asked this before, but searching I may not have, but I did find some similar quests with some interesting ideas including what may be most promising is tracking the "WM_MENUSELECT" and then replicate it (which I figured would be something like
Code:
SendMessage HwndMain, %WM_MENUSELECT, mak(dword, lo(word,1), Hi(word,%MF_SYSMENU)), hMenu
Anyways, I am sure it MUST have been asked and answered before, and I am just not searching the correct terms to find an example.
Eventually, I would like to write a routine that if running a tutorial, or a demo of the product, that I could actually show where the menu item is located (vs what currently I have to say stuff like "Tools--->Troubleshooting--->I have a problem with _______" instead of showing where the menu item is that could have a tool to solve your problem)
"Eventually" may be a ways off, but I figure if I can take "Baby Steps" showing the user why something opened rather than just calling the function that opens the tool, it could go a long way towards easing the users experience until the time I can take the time and "Hand-Hold" or "Walk-Thru" each step with each user
Comment