Re: What does "Finder could not get folder..." mean?
Re: What does "Finder could not get folder..." mean?
- Subject: Re: What does "Finder could not get folder..." mean?
- From: Chris Page <email@hidden>
- Date: Wed, 01 Aug 2001 13:32:30 -0700
nigh on 8/1/01 9:38 AM, Jon Pugh at email@hidden wrote:
>
At 6:06 AM -0700 8/1/2001, Chris Page wrote:
>
>> set pathList to pathList & (" '" & l & "'")
>
> ^^^
>
> It happens here. This sends a "get" event to the Finder, which returns the
>
> error.
>
>
You should probably include the proper coercion type (i.e. "l as string") so
>
that the get returns you something useful.
>
>
You didn't say whether this is under 9.1 or X.
This is on 9.1. And I tried adding "as string", "as text", and "as alias"
both with and without an explicit "get" if that matters.
Basically what I'm doing is copying new and modified files from a source
directory to a destination directory, then unlocking any locked files. This
script is invoked from CodeWarrior and is used as part of our build process
to copy all the ancillary files that go into the application bundle from the
source directory (where they are locked because they are sync'd read-only
from Perforce) to the project target destination. Since we have several
flavors of targets, doing a copy from a single location makes more sense
than trying to arrange for Perforce to sync the files into all the various
destinations.
I believe the script always works the first time, when there are no files in
the destination, and fails (not always) when there are files.
I think I'll try JollyRoger's suggestion of not wrapping the unlocking
process in a tell block, but I think I already tried a variation like that.
Cross your fingers.
--
Chris Page
Mac OS Lead, Palm Desktop
Palm, Inc.
One of the symptoms of an approaching nervous breakdown is the belief that
one9s work is terribly important. - Bertrand Russell