XYplorer 9.50 has been released on 06-Sep-2010. Here's a quick introduction to the main new features:
The interface is smart enough to handle a lot of different input formats. These are the rules and possibilities for such a list of names:
So, for example, the following item names would all select the file "Arial Unicode MS.php" in the current list:
Arial Unicode MS.phpUse Case: This interface enables you to perform a potentially large, complex, and not-rule-based multiple selection in a very easy and convenient way. There is no other way to do what Select Items... can do for you. Here's an example: Say you are going to overwrite 250 files in a folder of 5,000 files with newer versions. But you'd like to backup the original versions first. How will you grab those 250 out of the 5,000 without spending a tedious time with manual selection? Using Select Items... this is a snap: Go to the folder with the 250 new items and copy their names the clipboard (Ctrl+Shift+P); then go to the folder with the 5,000 items, click Select Items..., paste the 250 names into the text box, and click OK; all original items about to be overwritten are selected and ready for backup! This will take you less than 10 seconds.
You can restrict the selections to files or folders by attaching one of the following prefixes to the pattern:
*: Select files only \: Select folders only Examples: new* Select all items starting with "new" *:>new* Select all files starting with "new" \:>new* Select all folders starting with "new" It also works with RegExp: >^new Select all items starting with "new" *:>^new Select all files starting with "new" \:>^new Select all folders starting with "new" The prefix must precede any other prefix: *:!>^new Select all files NOT starting with "new" *:!type:doc Select all files where the Type does NOT contain the string "doc"
Examples:
!dir "%temp%" /p directory listing of the TEMP folder; DOS box stays visible !!regsvr32 "<curitem>" register the current item !!regsvr32 <selitems> register all selected items
The switch is /script=[script resource], where [script resource] can be:
1) The path to a script file (commonly called *.xys). The file spec is resolved as in the script command load, so you can skip the XYS extension. You can also skip the path if the XYS file is located in the default scripts folder. For example
XYplorer.exe /script=testwould run the file <xyscripts>\test.xys on startup. If the path contains spaces it must be quoted:
XYplorer.exe /script="C:\Zen\test one.xys"2) A script. It must be preceded by ::, and it must not contain double quotes or other characters that might lead to problems when parsing the command line. For example
XYplorer.exe /script="::msg 'Welcome to XY!';"Note the double quotes surrounding the whole argument which are needed because of the spaces in the script line.