Re: Finder Scripting
Re: Finder Scripting
- Subject: Re: Finder Scripting
- From: Dave Lyons <email@hidden>
- Date: Fri, 19 Aug 2005 17:12:38 -0700
On Aug 19, 2005, at 3:11 AM, Shane Stanley wrote:
Have a look at the dictionary: there's actually a command that
includes the words "(NOT AVAILABLE)" in the command itself.
There are actually 10 of those remaining (in the descriptions, not in
the actual names of the commands and properties). I'm not happy
about them, but they are there on commands and properties that worked
in Mac OS 9, where removing them entirely would have made it
impossible to compile e a script that (does version checking and)
works on both Finder 9 and Finder X.
When was the last release where the position property actually
meant something?
Of an item, or of a window?
I believe "position" of an item has worked since 10.0. It has never
meant the position on the desktop, and in Tiger there is a separate
"desktop position" property. (The regular "position" of an item that
happens to be on your desktop affects its icon-view position within a
Finder window targeting your desktop folder.)
The position and bounds properties of Finder windows have a more
twisted history. 10.3 was accidentally anomalous (toolbar height and
some window frame edges were accounted for differently than in 10.2),
and in 10.4 we believe we restored them to they way they were meant
to work. There are currently no bugs open on this topic, so please
let me know (or file a bug) if something is still broken.
I realize that having to write a script that supports the "broken"
version is a pain.
Who can keep track of which versions have "duplicate ... with
replacing" broken and which have "move ... with replacing" broken?
The details don't spring to mind here, but there seem to be no open
Radar bugs in this area. If something is still broken, please let me
know.
The current version of recording is pretty entertaining, too.
It went from "none" up to 10.2, to "some" in 10.3, and then "some
more" in 10.4. Is it entertaining because you have to guess whether
a given operation will record or not, or is something full-on
broken? The only open Recording bug is that closing certain kinds of
windows records the operation twice in a row.
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