• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: How to deal with Asynchronous Finder operations
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: How to deal with Asynchronous Finder operations


  • Subject: Re: How to deal with Asynchronous Finder operations
  • From: Jay Louvion <email@hidden>
  • Date: Tue, 20 Sep 2005 14:18:27 +0200

le 20/9/05 4:19, Dave Lyons à email@hidden est réputé(e) avoir écrit :

> 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:
> e.com
>
> This email sent to email@hidden

I think that indeed possibility 1 seems the mostadequate; In my personal
(though short) experience, when I wanted the physical size, I specifically
asked for it, without bothering about the physical size of "properties of"
bit...

I finally agree with Shane, though at the first glance, I was more
interested in the Nr 2 possibility; but it is errelevent to have a result
return sometimes, not everytime.

J.

Jay Louvion
Studio Casagrande
3, rue Müller-Brun
1208 Geneva

T+4122 840 3272
F+4122 840 3271

skypeme:
jaylouvion

www.studiocasagrande.com


 _______________________________________________
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

References: 
 >Re: How to deal with Asynchronous Finder operations (From: Dave Lyons <email@hidden>)

  • Prev by Date: Re. Search for a character
  • Next by Date: Re: Getting info back from iCal: missing values ?
  • Previous by thread: Re: How to deal with Asynchronous Finder operations
  • Next by thread: Re: How to deal with Asynchronous Finder operations
  • Index(es):
    • Date
    • Thread