--- Chris Nandor wrote:
Oh, that's the real important part I knew I was missing. You were passing
the string "newPath", not the contents of the variable C.
--- end of quote ---
Ha! Yes, I put some print statements in the perl and saw that it was passing
the string. At least I figured out one thi
At 15:21 -0400 2002.05.28, Katherine Richmond wrote:
>Also, in the AppleScript, I took the quotes off the argument and used the
>brackets:
>
>tell application "MacPerl"
> Do Script ["Pathology:Applications:Cron
>Software:ProcessPCImages2.pl", newPath]
>end tell
>
>I don't know if the bracket
--- Chris Nandor wrote:
Try [] instead of {} brackets. I am not sure if it makes a difference, but
it might. Also do $path = $ARGV[0], not @ARGV[0]. There might be
something else I am missing, but that should work.
--- end of quote ---
Chris,
$path = $ARGV[0] is what I needed in the Perl scri
At 12:12 -0400 2002.05.28, Katherine Richmond wrote:
>Thanks for your help. I am now returning the value, but I don't know how to
>pass
>it to the next MacPerl script. I call the first script like this:
>
>
>tell application "MacPerl"
> set newPath to Do Script "Pathology:Applications:Cron
>
--- Chris Nandor wrote:
The script needs to return a value via MacPerl::Reply($value). There are
other ways, but this is the easiest.
--- end of quote ---
Chris,
Thanks for your help. I am now returning the value, but I don't know how to pass
it to the next MacPerl script. I call the first scri
At 14:11 -0400 2002.05.24, Katherine Richmond wrote:
>Can you please tell me how I would do this?
The script needs to return a value via MacPerl::Reply($value). There are
other ways, but this is the easiest.
--
Chris Nandor [EMAIL PROTECTED]http://pudge.net/
Open Sourc
