Re: How to deal with Asynchronous Finder operations
Re: How to deal with Asynchronous Finder operations
- Subject: Re: How to deal with Asynchronous Finder operations
- From: Dave Lyons <email@hidden>
- Date: Mon, 19 Sep 2005 19:19:17 -0700
On Sep 19, 2005, at 5:16 PM, Dave Lyons wrote:
I have bug reports for "delete" and "empty trash" failing to block
On further investigation: "delete" should be blocking the script
ever since Mac OS X 10.1. (The remaining bug report of "delete"
failing to block was not from an AppleScript, but from some C code
sending Apple Events to the Finder directly, and using the option
"kAENoReply" when it wanted synchronous behavior.)
For those keeping score at home: The only scripted Finder operation
that is known to fail to block is "empty trash."
OK, so there are two: Getting the size or physical size of a folder
is known to return "missing value" if the Finder doesn't already know
the answer.
Opinions welcome: Assuming that I fix "get size of <folder>" to
block and wait for the correct answer (never return "missing value"),
what would be the desired behavior for "properties of <folder>",
which currently includes "size" and "physical size" properties? (1)
Always omit, (2) include if available, or (3) block until available.
I hesitate to choose (3), since interactively using "properties of
<folder>" from a script editor would suddenly get very slow.
Cheers,
--Dave
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Applescript-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden