Ok, I think I fixed that PT parameter handling. Maybe you like to try again.. o)
Sorry for any inconvenience.
@jinsight
When you try to copy "text", ClipboardEx expects the "text" in the clipboard to be file/folder paths. If you have "hello world" in the clipboard, actual text, nothing is gonna happen, because what should happen? ClipboardEx would need to come up with its own file name for what is in the clipboard (like DO does when pasting text into a folder). I am not sure it makes sense to handle this like DO (yet), but maybe someone will convince me. o)
EDIT: We could add a parameter to have a default file name for text data to be pasted, if pasting random text to folders is the actual intend, I don't think this is what you want though, but not sure. o)
The PT parameter now works as expected. Thank you!
Now that I know the definition of "text", your definition and its result make perfect sense. Making a new file from clipboard text is a different goal from putting existing items into a folder.
Yes, "text" means plain text with paths to files and folders you copied from an email or from a terminal output. This text content with list of files and folders can then be pasted as if you were using "Copy" on a regular file / folder selection before.
In the latest version of Opus, PASTETOFOLDERS is misbehaving slightly. In instances where the folder I am copying from is also included in the selected or specified list of folders to copy TO, the normal behavior used to be copy, copy, copy, etc. âoops, canât copy over itselfâ hitting âskipâ allowed the script to continue pasting to the rest of the list. Sometime in the last 1 or 2 Opus updates, hitting âskipâ is now phantom aborting the copy. The log shows the script continuing as if the file is being pasted, but the paste isnât happening.