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: Christopher Nebel <email@hidden>
- Date: Tue, 27 Sep 2005 09:44:19 -0700
On Sep 26, 2005, at 3:48 PM, Shane Stanley wrote:
On 27/9/05 1:33 AM, "Christopher Nebel" <email@hidden> wrote:
The correct answer is (3). (There is, by the way, a heuristic
for *not* including properties in the "properties" property, but
it doesn't apply here. "Typically, properties that can be
derived from other properties are not included, such as the
'reverse' property of a list.")
On that basis, surely "entire contents" should also be included --
then the
whole property can be labelled entirely useless for folders of any
size.
In fact, I read it the other way: "entire contents" (and in most
cases, "contents") can be derived by getting all the elements (maybe
recursively), so they don't need to be included, and, as you point
out, probably shouldn't be. Please write a bug asking for
clarification, and if you could, explain the logic that led you to
the reverse conclusion.
The missing "important bit" was probably that I was quoting from the
Scripting Interface Guidelines <http://developer.apple.com/technotes/
tn2002/tn2106.html>. They can be helpful to read even if you only
write scripts, because they illuminate certain interesting areas of
AppleScript, and if you see an application breaking them for no good
reason that you can discern, you can report a bug. =)
--Chris Nebel
AppleScript and Automator Engineering
_______________________________________________
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