In testing out a way to simplify a series of commands that I initially set up to run across several different buttons / three-button, I ran into a problem where the following doesn't work as expected when my current folder is a File Collection:
Select ALL
Clipboard COPYNAMES=path
Clipboard PASTE AS="D:\foo.txt"
...the files are selected, the expected text is copied to the clipboard, but the expected foo.txt file is never created. From trying Clipboard PASTE AS="D:\foo.txt" all on it's own in a button... this also does nothing when my current folder is a File Collection - so I'm guessing Opus is ignoring the 'Clipboard PASTE' command all-together since performing this action is not valid inside a File Collection?
Can you tweak it so that only variations of a 'Clipboard PASTE' command that DO NOT specify a valid folder path with the AS argument are ignored?
Hey there Daroc, yeah - but that's not surprising. The help manual says about the NOFROMFOCUS option:
So using that argument just reinforces Opus to run the command under the context of the sourcepath which in my case is the root of a File Collection. I understand why a Clipboard PASTE operation shouldn't work in a file collection if what you're pasting is text or image data from the clipboard (pasting a file you 'copied' to the clipboard DOES work, because it's just adding the file to the file collection). It's not a real folder, so you can't create a brand new 'Clipboard .' file in the root of something that's not real.
My contention and request here is that using the AS argument to specify a real/valid folder path to paste the file to shouldn't be blocked.
Totally unrelated... @Daroc, why do you bother to put /home/ in front of dopusrt? A call to dopusrt works without it - no?