Page 1 of 1

my teracopy script is broken

Posted: 05 Oct 2009 22:24
by calude
HI

was happy with Muroph's simple contr+c contr+x contr+v script but It broke down some weeks ago:
I now get this error:

The list of labels did not match any script in Script file 'C:\Program Files\XYplorer\Scripts\TC_copy.xys'.
load
C:\Program Files\XYplorer\Scripts\TC_copy.xys
tera-COPY


probably simple for YOU
:roll:

thanks

Calude

PS:
the script I am using is
example: TC_copy.xys

Code: Select all

// save list of items
  writefile("<xypath>\teracopylist.tmp", getinfo("SelectedItemsPathNames"));
  // get number of items
  $num = getinfo("CountSelected");
  // save operation and $num
  setkey copy, operation, tc, "<xypath>\teracopyvars.tmp";
  setkey $num, number, tc, "<xypath>\teracopyvars.tmp";
  // finished
  status "TeraCopy: Copy ($num item".(($num > 1)?"s":"").")", 78FF00, ready;

Re: my teracopy script is broken

Posted: 05 Oct 2009 22:38
by Muroph
1. what version of the script are you using?
i can't even remember the last version that had separate files for each command.

2. the script you posted as an example doesn't have any labels, hence the error message.
you should load the script without the "tera-COPY" part.

Re: my teracopy script is broken

Posted: 06 Oct 2009 11:15
by calude
Muroph wrote:1. what version of the script are you using?
i can't even remember the last version that had separate files for each command.
dont know either it just worked so I left it alone

Muroph wrote:2. the script you posted as an example doesn't have any labels, hence the error message.
you should load the script without the "tera-COPY" part.
I removed the labels and it worked for copy and cut

for paste I had to reenter the complete path to teracopy because it gave a file not found script error
there was a %programfile%/etc. type of path...

It works again

have a nice day

Calude

Re: my teracopy script is broken

Posted: 06 Oct 2009 16:27
by admin
Environment Variables... yes, yes. Relax everybody: if your scripts stopped working it's probably the recent Environment Variables related extra-smart code. Fix comes soon...