Context Menu "Open With"
- Thread starter CWBillow
- Start date
- Nov
- 250
- 2
The shell integrate thing that comes with 4nt does this for cmd files as well as btm files. I use it to run EXTPROC batches under cmd.exe shell.
You may look at http://www.maddogsw.com/cmdutils/ , which has utilities for context and propsfor, which opens the context menu, and properties sheet for any file it is "sent to", ie context myfile.jpg will open the properties sheet for that app.
You may look at http://www.maddogsw.com/cmdutils/ , which has utilities for context and propsfor, which opens the context menu, and properties sheet for any file it is "sent to", ie context myfile.jpg will open the properties sheet for that app.
- Jul
- 316
- 0
- Nov
- 250
- 2
I found a proggie called GDProps.exe at STaRDoGG/GeekDrop-Props
It opens the property dialog. Now i just have to figure out the context-menu.
It opens the property dialog. Now i just have to figure out the context-menu.
- May
- 13,210
- 180
As far as I know you get the same context menu in TCMD that you get in Explorer. I doubt there's any way to change that (because TCMD uses Explorer).
- May
- 13,210
- 180
Off-topic, new to me, and mildly interesting ... Windows 10 has OPENWITH.EXE which will present a GUI app selector ... prettier than the "Open with" context menu but with the same apps. OPENWITH.EXE's notion of current directory is your profile directory, so give it a full path to the target file.
My SYSUTILS plugin has SHELLEX, which can invoke registered verbs (plus "Properties") and PROPS which is just a wrapper for "shellex /c /v properties". SHELLEX fails (no surprise) when given "Open with". So I thought I'd try to figure out the "Open with" mechanism. Using ProcessMonitor, right-clicking a txtfile caused about 6500 registry events to be recorded. Moving the mouse to "Open with" (which expands itself) gave another 3000 events. I gave up.
My SYSUTILS plugin has SHELLEX, which can invoke registered verbs (plus "Properties") and PROPS which is just a wrapper for "shellex /c /v properties". SHELLEX fails (no surprise) when given "Open with". So I thought I'd try to figure out the "Open with" mechanism. Using ProcessMonitor, right-clicking a txtfile caused about 6500 registry events to be recorded. Moving the mouse to "Open with" (which expands itself) gave another 3000 events. I gave up.
- Aug
- 2,059
- 83
- May
- 13,210
- 180
It works today. It could be useful on Win7 which has no OPENWITH.EXE. On Win10, it gives tha same dialog as OPENWITH.EXE.
- May
- 13,210
- 180
And it doesn't work on Win10. It just fails silently. I'm very curious about why it fails. I couldn't find a signature for OpenAs_RunDLLW online. I dug it out of the SHELL32.PDB in the symbols directory for WinDBG on Win7. It looks like this (with its translation).
Code:
v:\> undecorate ?OpenAs_RunDLLW@@YGXPAUHWND__@@PAUHINSTANCE__@@PBGH@Z
void __stdcall OpenAs_RunDLLW(struct HWND__ *,struct HINSTANCE__ *,unsigned short const *,int)I can't do the same on Win10. Can anyone determine the signature of OpenAs_RunDLLW on Win10?
- May
- 13,210
- 180
Never mind; I got it. It's the 64-bit version of the same thing.
Code:
v:\> undecorate ?OpenAs_RunDLLW@@YAXPEAUHWND__@@PEAUHINSTANCE__@@PEBGH@Z
void __cdecl OpenAs_RunDLLW(struct HWND__ * __ptr64,struct HINSTANCE__ * __ptr64,unsigned short const * __ptr64,int)But it's __cdecl. And @CAPI doesn't work! Hmmm! ... I wonder why.