The DOpusRT tool can be used from outside of Opus to manipulate File Collections.
This functionality is accessed using the dopusrt.exe /col command - following /col you must supply a collection command, and the appropriate arguments for that collection command.
As with most command-line tools, if a path or other argument contains spaces, you must "put quotes around it".
Command | Arguments | Description |
---|---|---|
add |
[<flags>] <coll-name> <item> [<item> …] |
Add one or more items to the named collection. Example: |
|
[/dupeid=<id>] |
Lets you use "duplicate files" style collections by providing a numeric ID to assign items to groups. Items added with the same duplicate ID will be displayed together when the file display is grouped by duplicates. |
|
[/name] |
Lets you assign your own name to a duplicate group. This must be used in conjunction with the /dupeid flag. For example, |
clear |
[/full] <coll-name> |
Clears the contents of the named collection. Example: |
create |
[<flags>] <coll-name> |
Create a new collection. Example: |
|
/noclear |
Does not clear the collection if it already exists. |
|
/icon:<file> |
Specifies a custom icon for the new collection. |
|
/desc:<desc> |
Specifies a description for the new collection. |
|
/dupes |
Marks the collection as a "duplicate files" collection. |
|
/query |
Creates the new collection as a stored query. |
delete |
<coll-name> |
Delete the named collection. Example: |
export |
[<flags>] <coll-name> <export-file> |
Export the contents of a collection to a text file. If the encoding type is not specified (using the optional flags), the file will be encoded as UTF16-LE if any filenames require Unicode, and otherwise in the current ANSI code-page. Example: |
|
/append |
If the export file already exists, append to it - otherwise it will be overwritten. |
|
/utf16be |
Force encoding to UTF16-BE. |
|
/utf16le |
Force encoding to UTF16-LE. |
|
/utf8 |
Force encoding to UTF8. |
|
/ansi |
Force encoding to the current ANSI code-page. |
|
/cp:<codepage> |
Specify the code-page. |
import |
[<flags>] <coll-name> <import-file> |
Import the contents of a text file to a
collection. |
|
/clear |
Clear the collection before importing the new items. |
|
/create |
Create the collection if it doesn't already exist. |
|
/nocheck |
Don't check that the items listed in the import file exist before importing them into the collection. |
|
/relative:<path> |
Specify the path which lines in the list are relative to, if the file
does not contain fully qualified paths. If not specified, paths are
assumed to be relative to the same folder the list is in. |
|
/utf16be |
Assume UTF16-BE if no BOM. |
|
/utf16le |
Assume UTF16-LE if no BOM. |
|
/utf8 |
Assume UTF8 if no BOM. |
|
/ansi |
Force conversion from the current ANSI code-page. |
|
/cp:<codepage> |
Force conversion from a specific code-page. |
remove |
<coll-name> <item> [<item> …] |
Remove items from a collection. |
rename |
<old-coll-name> <new-coll-name> |
Rename a collection. |
runquery |
<coll-name> |
Run (refresh) a stored query. |
setdesc |
<coll-name> <desc> |
Set the description for a collection. |
seticon |
<coll-name> <icon-file> |
Set a custom icon for a collection. |
setpaths |
[<flags>] <coll-name> <path> [<path> …] |
Set the search path or paths for a stored query. |
|
/add |
Add the paths to the query, don't remove any existing ones. |
setquery |
[<flags>] <coll-name> <query> |
Set the query string for a stored query. In conjunction with this, you can use the /engine argument to set the search engine used by the query. The default is Windows search; other options are everything, everythingglobal and opus. Example: |
|
/auto |
Set the stored query to "auto refresh" mode - the query will be run/refreshed whenever it is loaded. |
|
/noauto |
Set the stored query to not automatically refresh. |