Re: File not ready for reading
Re: File not ready for reading
- Subject: Re: File not ready for reading
- From: Shane Stanley <email@hidden>
- Date: Mon, 18 Mar 2013 10:15:40 +1100
On 18/03/2013, at 7:16 AM, Christopher Stone <email@hidden> wrote:
> We've been fussing about file(locking/busy) issues since the mid 90's.
That's unix for you.
FWIW, OS X 10.7 did introduce a new way of dealing with the issue. (You probably remember the demos of attachments in emails being updated as the originals were modified.)
But it needs to be supported by all the apps involved -- it's supposed to be supported by the Finder, but unless the app writing the original file also supports it, it's of no use in Luther's case. (It involves apps effectively communicating with each other via a file coordinator, so all parties need to be on board, and it's only meant for files that users can normally view and edit.)
In theory a quick look suggests it should provide a way of getting around some of the worst cases -- certainly cases where one is waiting on a Finder write. You wouldn't want it evoked on every AS read or write, because it can have consequences you might not want (ie, forcing an app that has the file open to do a save, and perhaps generally being slower), but it might be useful as an alternative read/write mechanism. Because it involves inter-app communication it may well need to be an application-level command. There's a thought...
--
Shane Stanley <email@hidden>
'AppleScriptObjC Explored' <www.macosxautomation.com/applescript/apps/>
_______________________________________________
Do not post admin requests to the list. They will be ignored.
AppleScript-Users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
Archives: http://lists.apple.com/archives/applescript-users
This email sent to email@hidden