extra windows memory

Question

3.00/5 (3 votes)

See more:

Whenever a user select one or more files or folders in windows explorer and right click to cut or copy the selected objects,
i have to disable pop up menu's cut and and copy options for particular type of files(i.e for file having .doc extension , pop up menu should not display cut or copy options).

Ya, i know that i have to process WM_INITMENUPOPUP message.
but how could i know what is currently selected in Window explorer application.

I don't know ,what window-extra-memory of windows explorer does contain?

from where i can get list of objects selected so as i can correctly process WM_INITMENUPOPUP ?

Can any one give me guidance?

Thanks in Advance.

Posted 18-Apr-11 0:40am

Zubin 2

Add a Solution

2 solutions

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Sergey Alexandrovich Kryukov · Answer 1 · 2011-04-18T07:47:00

This should provide you with a walk-through: Use Shell Context Menu in your applications[^].

Note some things: it has nothing or almost nothing to do with "extra Windows memory"; I have no idea why you consider these concerns related. Right term for the menu is "Context menu". Prefer disabling of the items to hiding them. No, it will affect not just the Windows Explorer but any file manager or any other code based on Shell API — be aware of it. Some file managers will have different commands added to the Context Menu, like "Move" in one step. There are many other ways to manipulate file, using the console, first of all. See also the notes by Nishant he posted in his Solution.

That said, if you think your Context Menu can provide some kind of file protection, think again: it won't, whatever you do with the Shell.

Finally, I'm not sure you really need to do this work (unless you want to register really serious application to work via Shell interface; a very successful example is such approach is TortoiseSVN, http://en.wikipedia.org/wiki/TortoiseSVN[^]).

If a Word document is opened, it cannot be deleted/moved anyway as Word keeps it open without shared access. If you simply use Word automation, it will always behave like that. In all other cases, you can do the same.

—SA

Nish Nishant · Answer 2 · 2011-04-18T07:55:00

Solution 2

[Adding to SA's response.]

Merely disabling copy/cut in the context menus won't help prevent people from copying the file. They can use keyboard shortcuts. They can use a console app to do it, or do it programatically by specifying the full path. They can copy a parent folder that contains the document. In fact by mapping the drive across a network, they can do it across the network from another machine. Keep this in mind too.

Posted 18-Apr-11 7:55am

Nish Nishant

Comments

Espen Harlinn 18-Apr-11 17:45pm

Good point, my 5

Sergey Alexandrovich Kryukov 18-Apr-11 22:17pm

You're absolutely right, I should have mentioned that myself (I'll reference this post by updating my solution).
My 5.
--SA