How to test a button command

Help & Support
1

When testing a button I often forget how to output the text so that is looks correct.
I also see a other people - and myself - asking questions which they could prob solve if they could easily see what the output of a command might be, making it easier to try a few different combinations to get the right result.

What is the best way to do this. Also can I suggest a sticky in the buttons forum describing the best method?

This is how I do it, once I remember

@leavedoswindowopen @nofilenamequoting echo <inser command here> @nodeselect
Example

@leavedoswindowopen @nofilenamequoting echo {sourcepath}{file} echo {destpath}{filedest} @nodeselect

2

I often do something similar (only using the Pause command instead of @leavedoswindowopen), but it's also worth mentioning that extra processing can happen with DOS Batch buttons which doesn't happen for normal buttons.

e.g. Percent characters are doubled-up in filenames to avoid DOS treating them as something else.

It usually makes no difference, but it's worth keeping in mind.

Steves DopTest tool is another way to see the command line that Opus has generated, and doesn't require the button be changed to DOS Batch mode.