A button that moves an element to the destination lister and them select the moved file.?
Copying an element to the destination lister, then change the creation date of the copied element in the dest lister.(set the current date).
How I do this?
come on any help?
How about letting folks finish their workday before "bumping" eh??? 
I tried a few things like:
Copy MOVE
Set SOURCE=Toggle
Select "{o}"
...and some other tricks, but nothing really worked... One problem with trying to do this is that the Select command seems to not operate on full paths. Else I'd have thought you could have used something like Select {d}{o}. The only thing that selects files in the "other" lister display are the SOURCETODEST and DESTTOSOURCE arguments, but those don't seem to work once the file has been moved from it's source and is no longer "selected" in order for Opus to match in the other lister side.
You were close, Steje. I think this works, via a bit of dopusrt voodoo to make the Select command(s) work on the new source instead of the original source:
Copy MOVE
Set SOURCE=Toggle
dopusrt /cmd Select "{o}"
Actually - I "had" tried that based on my long-standing appreciation for dopusrt tricks ... but it didn't change the results. And adding dopusrt /cmd in front of all three of the commands didn't always work with multiple files being moved...
But since you just mentioned it here in your reply - I went around and played around even more, and in a monument to ugly over-use of dopusrt (probably have some in there that I don't need) and some skipping back and forth between source and dest - I came up with this fugly and roundabout way of getting "the job" done...
dopusrt /cmd Set SOURCE=Toggle
dopusrt /cmd Select NOPATTERN HIDEUNSEL
dopusrt /cmd Set SOURCE=Toggle
dopusrt /cmd Copy MOVE
dopusrt /cmd Set SOURCE=Toggle
dopusrt /cmd Select ALL
dopusrt /cmd Select NOPATTERN SHOWHIDDEN
Hmm, it did work for me, but maybe there is a timing issue where the Select can be run sometimes before the other side has detected the new file.
Probably the case - the Select command seems to be particularly sensitive (compared to other functions) to oddball timing issues... All I can say is that I tested with several very small "5 byte" text files... and the result I get is that usually the "first" (out of multiple files "moved" in a single button click) file gets selected in the destination, while the others are not.
Even if a strange timing issue, my last FUGLY method is something I would presume would work in all cases... just look away from the screen while the file display border color changes back and forth from the multiple source/dest togles 
...
Detection of file changes, especially in inactive file displays, is asynchronous with the running commands, so the Select command can be run before the file display lists the thing you're trying to select.