I have a folder that contains numerous subfolders inside subfolders, and endless files. I need to print out the entire folder tree, to use as reference when handling the files. Please note, I only need to print the folder tree, not the contents of the files themselves. The only relevant option I found was to revert to flat view and then copy all filenames to the clipboard, but that is flat text style and does not provide a clear tree-like view of the structure. Is there a way to do this in Dopus or should I submit it as a feature request?
I've already submitted this sort of thing (I think) as a feature request - feel free to do so as well. The only way to accomplish the same effect I think you're looking for is to change the folder format options for the Print Folder dialog and edit the Column tab to include the 'Location (relative)' and 'Filename' columns - and set the Location column to be listed and sorted first. If you have very long directory and/or file names, you may need to tweak your column widths, or else the test file you put this into will truncate whatever names that exceed your column width with periods...
You'll end up with the relative folder path shown to the left of each file, which if you want to view in a more eaily viewed 'tree format' you'll then need to remove and indent. Requires a bit of 'fixing up' in a text editor, but it's the only alternative I've come up with.
The request is to provide a hierarchical tree view listing with Print Folder similar to what you see in the Lister if you enable flatview with the 'grouped' option.
A trully useful command that had skipped my attention. So far, I was trying to work around the problem with dir *.* /b /s >whatever.txt but this is much better.
[quote]Ive been trying various combinations of:
tree \ clipboard \ copy
a DOS window flashes, but i get nothing much on clipboard apart from tree or copy depending on the sequence[/quote]
Grab my SetClip program and stick SetClip.exe in C:\Windows\System32 then paste this Opus button on to your toolbar while in Customize mode:
<?xml version="1.0"?>
<button display="both" effect="gray">
<guid>{D3D44FAD-DF9F-4966-BEC8-C96692DBFAE2}</guid>
<label>Folder Tree to Clipboard</label>
<icon1>162</icon1>
<function type="batch">
<instruction>runmode hide</instruction>
<instruction>Tree /A >folder_tree_temp.txt</instruction>
<instruction>SetClip -f folder_tree_temp.txt</instruction>
<instruction>del folder_tree_temp.txt</instruction>
</function>
</button>
If you want to see filenames as well as directories in the output, add the /F switch after the existing /A one on the Tree line. (You might see "folder_tree_temp.txt" in the output then, heh, but you could fix that by writing the file to a temporary directory instead of the current directory.)
I tried this and it worked well also... though not at first, and then I realized why.
It's a bit off topic, but everyone should be wary of running certain types of buttons from 'floating' toolbars. Some things (like current folders) don't get operated on like you'd expect when running a function from a floating toolbar vs. a docked one... For instance, running the button above causes tree to run against the %temp% folder... rather than the current folder. I guess floating toolbars really don't have any good way of telling which lister to relate to... Just an incidental FYI.
I think if you explicitly add in the appropriate {} sequence you can get the source/destination folder into a floating toolbar's command (and this usually happens automatically for internal commands).
You could either CD a the top of the file (hint: Use the /D switch to make the CD command work across different drive letters in an MS-DOS batch file/button -- but not in other types of Opus buttons/commands) or change the commands so they run on and output to specified paths.
