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: Shane Stanley <email@hidden>
- Date: Tue, 27 Sep 2005 08:48:57 +1000
- Thread-topic: How to deal with Asynchronous Finder operations
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.
It's my understanding that the "properties" property was invented for
QuarkXPress (hence the 'qpro'), either by Dave Shaver or Cal Simone. Users
of QXP will know that if you ask for the properties of any of the classes in
its Text Suite, the list does not (at least, it used not) include the
"contents" property. This always struck me as an excellent decision on the
basis of performance -- a victory for common sense.
Now, if every application was a stickler for the AS guidelines, I could
almost understand sticking to them at the cost of performance. But that
particular stable door was left swinging many years ago, so the occasional
transgression in favor of the user doesn't strike me as too bad at this
point.
--
Shane Stanley <email@hidden>
_______________________________________________
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