Give the following a try and see if this works for you. It is a lot faster and
does not come with the annoying chime when it finishes the copy.
on csCopyFolder tSource, tTarget
if the platform is "MacOS" then
csDebugOutput ("## csCopyFolder Handler Running...") --*DEBUG*
I have a copyfile in pure LC that's fast (nuch more than Applescript) and
should be easily extensible for folders.
I am traveling now, ping me in 10 days or off-list earlier if it's that
urgent and we'll wirk something out.
--Maarten
On Wednesday, August 24, 2011, J. Landman Gay
wrote:
> I do u
I do use "create folder" so that does seem to point to the problem, only
in my case I don't even need to issue that command for the name-check to
fail. What it looks like from an uneducated view is that somehow the
Finder's database is updated to include a non-existent folder.
The odd part is
rked. Not sure why. Maybe it just
ignores some error that is generated. That ended up as the solution to the
problem. I just left the in the try block.
Martin
--
View this message in context:
http://runtime-revolution.278305.n4.nabble.com/revcopyfolder-problem-tp3766036p3766335.html
Sen
Thanks Ken, Jacque,
I know the result indicates an applescript problem, I should have
clarified a bit by asking if the user could do something in his system
that would cause the applescript problem?
Jacque the problem sounds similar. My app creates a folder in the
library/app support folder. That
Thanks Ken, Jacque,
I know the result indicates an applescript problem, I should have clarified a
bit by asking if the user could do something in his system that would cause the
applescript problem.
Jacque the problem sounds similar. My app creates a folder in the library/app
support folder. Th
On 8/24/11 1:05 PM, Ken Ray wrote:
On Aug 24, 2011, at 12:10 PM, ron barber wrote:
Hi,
A user is reporting a problem with my software and I have traced it
back to an opening call to revcopyfolder. He is on a Mac 10.6. I sent
him two other stacks that simply call revcopyfolder and they fail,
re
On Aug 24, 2011, at 12:10 PM, ron barber wrote:
> Hi,
> A user is reporting a problem with my software and I have traced it
> back to an opening call to revcopyfolder. He is on a Mac 10.6. I sent
> him two other stacks that simply call revcopyfolder and they fail,
> returning execution error in t
Hi,
A user is reporting a problem with my software and I have traced it
back to an opening call to revcopyfolder. He is on a Mac 10.6. I sent
him two other stacks that simply call revcopyfolder and they fail,
returning execution error in the result. The paths check out and I
have never had a report
