Tree movement description

What is meant by "move up/down the directory tree"? To understand it open the treeinfo.wc file built by Total Commander. You'll see all the directories of some logical disk in the directory structure order.

Where treeinfo.wc can be found? By default - in the root of each logical disks. It's easy to do the following:

• Open Find Files (Alt+F7) window - see screenshot;
• In the "Search for" field indicate treeinfo.wc (1);
• In the "Search in" field (2) indicate all disks of interest, or just press "Drives" (3) and select "local harddisks";
• To save time, you can open the dropdown list and select "current dir only" (4).

If the search fails, it could be due to two reasons. First, you've never give commands of the cm_SrcTree family, and the cm_CDtree (Alt+F10) command. Second, your wincmd.ini has TreeFileLocation and TreeFileLocationE keys with non-empty values.

If so, you can force Total Commander to build the treeinfo.wc file, for example, by pressing Alt+F10.

This or that way, but suppose that treeinfo.wc is available. Then you can realise what the "directory structure order" is - it's just alphabetical order of full paths of all directories of a disk.

"Tree view", "CD Tree", and, finally, "separate tree" are visulalising this directory structure order. So, if you move down the directory tree, you pass to the next (lower neighbour) directory relative to the current one, when moving up you go to the previous (upper neighbour) directory. These are actions that my scripts perform. What are advantages of script over the Tree View?

• The "Tree View" behaves like Windows Explorer and have almost the same drawbacks. That's why I prefer Total Commander to Explorer. I hope you also do;
• Sometimes you can't use both panels in Tree View. If you change disk in the opposite panel, the tree panel changes, too. The script does not care about the target panel at all;
• If the treeinfo.wc file does not exist, it takes too much time to build it;
• If you need to move to the previous directory, you have to perform too many operations: switch to another panel, activate tree view, wait for the tree to be built and, finally, press the Left key. With the script it's enough to press one button or one hotkey.

If you reach the first (root) directory on the current disk and run the script again, you can go to the previous disk after confirmation. Thus, you can visit all directories of your computer. The same is valid when moving down with another script. After passing to the last direcctory on a disk (represented by the last line of the treeinfo.wc file) you'll get the invitation to visit the next disk.

In this section three pairwise (up/down) scripts are presented. Why they differ? When use this or that?

• Scripts TreeDownCmd and TreeUpCmd, as their names demonstrate, are using internal Windows command dir. Parameters "%p", "%n" are passing from Total Commander to scripts as usual.

• Scripts TreeDownX and TreeUpX require the Xxcopy application. That means that you must at least download and install it, and also indicate the Xxcopy path in the script code. On the other hand, these scripts are slightly faster. Moreover, they can work with national alphabets, that's why I prefer these two.

  Be careful: this script call differs from usual way! If you want to run the script by the Total Commander button, you must do the following:

  • In the "Command" field indicate d:\Utils\PowerPro\powerpro.exe *script runfile TreeUpX=, and replace d:\Utils\PowerPro\powerpro.exe with the actual PowerPro path for your computer. Replace TreeUpX with the actual name of this script if you've changed it for some reason (though you should not). Don't forget the = (equality sign) after the scrip name!;

  • In the "Parameters" field indicate %P%N without quotes.

  It's a good idea to assign the Alt+PgDn and Alt+PgUp hotkeys to TreeDownX and TreeUpX scripts, respectively.

• TreeDownXMouse and TreeUpXMouse scripts are generally equivalent to the latter two. They also need Xxcopy that is denoted by the "X" letter in names. The difference is that TreeDownXMouse and TreeUpXMouse do not need any parameters passed from Total Commander. What are advantages of this peculiarity? You can call these scripts from outside Total Commander, for example, from a PowerPro bar. Take my configuration file and simply import it to PowerPro, and that's all.

  Another way to execute these script is so called mouse movements. I prefer the following: if to scroll the mouse wheel forward and then back, the previous directory is opened in Total Commander, and vice versa, back-forward wheel movement corresponds to the next directory (down the tree). To do so, open the PowerPro configuration, then the "Key/Mouse" tab, then press the "New" button, and, finally, do exactly as it is shown on the screenshot:

  

  Press OK, then "Clone", open new line properties and replace "TreeDownXMouse" with "TreeUpXMouse", and "wheel back/forward" with "wheel forward/back".

• After commands cm_GotoNext, cm_GotoPrev, and cm_GoToLast were introduced in version 9.50, I have developed new versions of scripts. I called them TreeDownTC and TreeUpTC. They have many advantages over all the above one. First, they work faster. Second, they don't need any external tools. Third, they don't require any parameters.

Attention: Scripts TreeDownXMouse, TreeUpXMouse, TreeDownX and TreeUpX work only with Xxcopy version 3.0 and later! If your version is older, either update Xxcopy or use these scripts:

TreeDownXMouse
TreeUpXMouse
TreeDownX
TreeUpX

So, here you are:

Down (+cmd) – TreeDownCmd
Up (+cmd) – TreeUpCmd

Down (+Xxcopy) – TreeDownX
Up (+Xxcopy) – TreeUpX

Down without parameters (+Xxcopy) – TreeDownXMouse
Up without parameters (+Xxcopy) – TreeUpXMouse

Down with internal commands – TreeDownTC
Up with internal commands – TreeUpTC

Main Page