 |
|
 |
First thank you for your great work ! but I think icon is more beautiful than bitmap , Can you tell me how to do that ?
|
|
|
|
 |
|
 |
Are you asking how to use an icon, instead of a bitmap, for the menu item image?
Check out MENUITEMINFO. Look for usage in the source code... modify as needed. Use MIIM_BITMAP in fMask. Use HBMMENU_SYSTEM or HBMMENU_CALLBACK maybe. Good luck!
|
|
|
|
 |
|
 |
Hi,
How can I add entries to the Desktop menu that Windows displays when the user right-clicks on an empty area on the desktop? (NOT the menu that is displayed when the user right-clicks on a folder/icon etc but the menu that is displayed when the user right-clicks on an EMPTY area).
Thanks!
|
|
|
|
 |
|
 |
Add your shell extension here:
HKCR\Directory\Background\shellex\ContextMenuHandlers
|
|
|
|
 |
|
 |
Firstly, thanks for a very usefull utility. It's better in every way than the XP PowerToys shell extension.
One suggestion I have that is the ability to open a command shell from a file rather than a directory, i.e. the command shell would be opened at the directory containing the file I right clicked.
|
|
|
|
 |
|
 |
I tried to compile the VC6.0 version you have provided but it gave errors on two lines:
1. 'CContextMenu' : cannot instantiate abstract class due to following members: see declaration of 'CContextMenu'
2. 'DWORD_PTR' : undeclared identifier
I can manage the second one, but have no clue about CContextMenu error.
Please help.
Arshad Parvez
|
|
|
|
 |
|
 |
- It would be nice to be able to select multiple filenames at once. (I mailed you a patch that implements this - don't know if you received it)
- In addition to file paths, it would be handy to be able to just to copy file names
- When launching a program with command line args, the program's working dir could also be settable and/or default to where the .exe is located.
|
|
|
|
 |
|
 |
If you add more items you might want to consider a cascading menu like winace and winrar use in order to keep the menu less cluttered.
|
|
|
|
 |
|
 |
This article is quite cool as it show how to easily get some Context Menu Handler put in place.
The features provided are also cool , I've been using Ninotech's Path Copy for a couple of years now (version 4.0 latest) and find it as an essential part of my tool kit.
Again, NOT to distract from the article,
Thanks, Well Done.
AllenR
|
|
|
|
 |
|
 |
...i've seen all kinds of context menu handlers
but none to allow the user to insert a new menu
entry easily and flexibly. I hope there is something like
this out there but i havent seen it so far.
OS/2 has this since ages but then os/2 has an
OO shell so the user can efectively say
'when this menu entry that i just added to this
particular menu is invoked do this' where 'this' is
whatever he can do with the shell via direct manipulation
(usually through the mouse).
Since explorer isnt that OO (on 21st century? ouch!)
someone could make a tool to allow the user to insert the
menu entry at the menu of her choice and at minimum allow
her to fire up her command from there, which could be an
.exe, a script etc etc. Plus, since many of the operations
explorer does are performed through a 'rundll' call with
some bizzare parameters the tool could include as many as
possible of these to allow maximum shell integration with
the user menu entry invocation. Tc
|
|
|
|
 |
|
 |
I think that is what the "Send to" menu is for. You wouldn't want non-context sensitive menu item on there would you?
|
|
|
|
 |
|
 |
It never occurred to me to write a shell extension to accept command line parameters. I'm also impressed that you supplied a VC6 version too.
|
|
|
|
 |
|
 |
Thanks for the kind words!
-Shaun
|
|
|
|
 |
|
 |
Well i am not able to register ure dll,
as well project is not opening in VC7.0 saying it is version 7.01
can u post a project in VC7.0 or 6.0
|
|
|
|
 |
|
 |
You need MFC71u.dll and msvcr71.dll to use the prebuilt utility. I updated the artical... waiting on review for the update to post. In the mean time you can get the files you need here:
MFC71u.dll
msvcr71.dll
Sorry for the trouble.
I'll see what I can do about digging up my older project files for you ASAP.
-Shaun
|
|
|
|
 |
|
 |
I have a vc60 version... the code base is out of date but it works... I can send it to you if you want me to. Really the best thing to do would to make your own vc60 MFC DLL project, update the app object and stdafx.h with any mods made to mine, and pull my other implemetation files into your project. My source should be ready for localization too, if you're into it.
-Shaun
|
|
|
|
 |
|
|
 |
|
 |
BTW - I updated the code in the vc6 project to be in sync with the vc1 project.
-Shaun
|
|
|
|
 |
|
 |
Because I have VC++ 6.0, my interest is with those set of files, utilities, dll's (etc.) that represents the complete and successful working of your sample.
Having downloaded both the source code and utility files for this version from the link you listed above, I was able to obtain a clean compile and link. However, there was no executable built. Could you explain why this was?
Perhaps of interest is this, that even though I downloaded the VC++ 6.0 version of the utility files, when I built the application, I noticed a CMDCMX.dll file was created of size 129 KB. Contrast that to the other 'dll' file you presented for VC++ 6.0 whose size was only 36 KB.
The program I was able to compile and link, seemed to have used the CMDCMX.dll file. So the question is, "Do I absolutely need the VC++ 6.0 version you offered, or could I stick with the CMDCMX.dll version?"
Thanks for any help you can offer. (I would really like to get this sample to work!!)
William
Fortes in fide et opere!
|
|
|
|
 |
|
 |
It failed to build the executable because the executable's "project" was not the active project. In the project pane right click on the cmdcmxcfg project and select "set as active project". This cmscmxcfg project has a "depends" on the cmdcmx project and will thus build both.
The size difference is because you built "debug"... switch to the "release" build to get smaller and faster binaries.
Hope this helps!
-Shaun
|
|
|
|
 |
|
 |
Your shell extension requires MFC71U.DLL and MSVCR71.DLL. It is better if you could include it in your download.
Sonork 100.41263:Anthony_Yio
|
|
|
|
 |
|
 |
Thank you. The issue I had with posting them is that if everybody that needs them in their demos posted them a lot of space would be wasted on the server.
I have an updated version of the readme ready to post but was waiting for some feedback from the site monitors. I'll post the things on my site and post a link in the artical if the codeproject does not have a redistributables folder.
Again, thank you very much for the feedback.
|
|
|
|
 |