If you drag using the right mouse button, a menu appears with the commands
Move Here, Copy Here, Create Shortcut(s) Here, and Cancel. Click the
command you want.
fFlags
Flags that control the file operation. This member can take a combination of the following flags:
FOF_ALLOWUNDO
Preserve Undo information, if possible. If pFrom does not contain fully qualified path and file names, this flag is ignored.
FOF_CONFIRMMOUSE
Not currently used.
FOF_FILESONLY
Perform the operation on files only if a wildcard file name (*.*) is specified.
FOF_MULTIDESTFILES
The pTo member specifies multiple destination files (one for each source file) rather than one directory where all source files are to be deposited.
FOF_NOCONFIRMATION
Respond with "Yes to All" for any dialog box that is displayed.
FOF_NOCONFIRMMKDIR
Do not confirm the creation of a new directory if the operation requires one to be created.
FOF_NO_CONNECTED_ELEMENTS
Version 5.0. Do not move connected files as a group. Only move the specified files.
FOF_NOCOPYSECURITYATTRIBS
Version 4.71. Do not copy the security attributes of the file.
FOF_NOERRORUI
Do not display a user interface if an error occurs.
FOF_NORECURSION
Only operate in the local directory. Don't operate recursively into subdirectories.
FOF_NORECURSEREPARSE
Treat reparse points as objects, not containers. You must set _WIN32_WINNT to 5.01 or later to use this flag. See Shell and Common Controls Versions for further discussion of versioning.
FOF_RENAMEONCOLLISION
Give the file being operated on a new name in a move, copy, or rename operation if a file with the target name already exists.
FOF_SILENT
Do not display a progress dialog box.
FOF_SIMPLEPROGRESS
Display a progress dialog box but do not show the file names.
FOF_WANTMAPPINGHANDLE
If FOF_RENAMEONCOLLISION is specified and any files were renamed, assign a name mapping object containing their old and new names to the hNameMappings member.
FOF_WANTNUKEWARNING
Version 5.0. Send a warning if a file is being destroyed during a delete operation rather than recycled. This flag partially overrides FOF_NOCONFIRMATION.
As you can see MS has thought about it (FOF_CONFIRMMOUSE) and decided not to do it. File Manager had this option. But Explorer got an Undo command instead. If they change their mind (and they haven't in 10 years) then they can add it in without breaking older applications.
Thanks for your help. Based upon the other reply to my originial post, I was
thinking of how the old File Manager worked. The reason for this post in the
first place: At work we have a new person who twice in one week moved folders
and files by accident.
Thanks! You are correct, I was thinking of the old File Manager. The reason
for the question was because we have a new person in our group who moved
folders and files by accident.
This is a good user interface principle. Do not bombard users with dialog boxes - they won't read them anyway.
Only one type of user reads dialog boxes, medium experienced users. Advanced and beginners don't.
Ask a Question
Want to reply to this thread or ask your own question?
You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.