Probably a silly question but... where is the test mode?

Help & Support
1

[quote]Opus provides comprehensive filter functions for Find, recursive Copy and Delete, and Rename functions. These
filters support Opus’ wildcard pattern matching or full regular expressions. A unique test mode even allows you
to test whether your pattern matching syntax is correct before you commit to the file actions for real.[/quote]

This is quoted from the reference manual page 14, and seems rather useful..
however, I can't seem to find it.

Not in Copy or Delete functions (when copy/delete filters are checked) at least, and as the above specifies that it should be there.. and those are really the functions which would benefit the most from a test mode.

I've located it in the Output window of the Find function though, and I guess it's available in Rename..

I've tried searching the forum for a clue, but the search function of the forum is... not good..

I've tried searching for: test mode, "test mode", test AND mode, etc, in both search modes, with lots of results, except any and all results matches one of the words, and not the phrase as intended.

2

Correction, I thought I had found it for the find window, but not really,
probably not particulary necessary from find either.

No clue about how to get any output to the test page, from anywhere..

3

Hi,

After selecting one or more files, try 'File > File Commands > Rename'. You can set your rename criteria and there are buttons labeled 'Preview' & 'Test' near the bottom. You can assign this to a button, if it isn't already on one, or just use the menu structure.

Mike

4

[quote="mnoble"]Hi,

After selecting one or more files, try 'File > File Commands > Rename'. You can set your rename criteria and there are buttons labeled 'Preview' & 'Test' near the bottom. You can assign this to a button, if it isn't already on one, or just use the menu structure.

Mike[/quote]

Yes, I've found the 'test' and 'preview' options in rename, but not
in copy/delete functions, where it, as mentioned in the quote I posted,
should be.

Maybe this is an error in the reference manual, or maybe its something that was documented, but not implemented.