Re: Busy Status
Re: Busy Status
- Subject: Re: Busy Status
- From: Chris Page <email@hidden>
- Date: Sun, 3 Nov 2002 16:07:13 -0800
On Saturday, Nov 2, 2002, at 19:55 US/Pacific, Jon Pugh wrote:
At 6:26 PM -0500 11/2/02, Rob Jorgensen wrote:
I guess Jon's 'fileIsBusy' hasn't made it to X but I mention just in
case.
Yep, it's in the OS X version (thanks for the nudge) but it doesn't
work either (not the way I want it to anyway). ;-) According to the
description, it tells whether or not a file is open. Based on my
tests with Jon's Commands, Standard Additions and the Finder, a file
that is in the process of being downloaded presents a challenge when
trying to determine its busy status. <shrug>
OSX changes the way files are shared. No longer does have having a
file open for write access prevent another process from opening it for
write access, which prevents this command from working. I'm looking
into what it would take to fix this, but I haven't found anything
worth implementing yet, and if I don't, I'll probably just remove the
command.
Mac OS X 10.2 Jaguar introduced a built-in file access locking
mechanism for applications that use the Carbon File Manager, so the
pre-X behavior has been restored.
I just ran a test, and "open for access ... with write permission"
correctly returns an error on a file open in another application, but
fileIsBusy on the same file returns false. fileIsBusy returns true if I
"open for access" the file beforehand in the same script. So there may
be a way to get fileIsBusy to work, but it might involve trying to open
the file, rather than testing the file status bits.
--
Chris Page - Mac Guy - Palm, Inc.
The solution to software piracy is to reduce your COG to zero, which
is left as an exercise for the reader.
_______________________________________________
applescript-users mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/applescript-users
Do not post admin requests to the list. They will be ignored.