Re: Finder scripting bug
Re: Finder scripting bug
- Subject: Re: Finder scripting bug
- From: Matt Deatherage <email@hidden>
- Date: Mon, 16 Jan 2006 13:26:08 -0600
On 1/16/06 at 12:28 PM, Nigel Garvey
<email@hidden> wrote:
> A bug is a bug (or not) whoever reports it. What's the avenue for
> responsible, paying customers who are not "registered developers" to
> point out faults in the software? Apart from whinging in their local
> forums, that is?
I'm not sure I want to know how to whing in any forum.
I extracted a few paragraphs here, but in general, programmers
(including AppleScript programmers) have a fairly good idea of what is
a "bug," and what is "working as designed even if it's not what you
want." Users - not so much. *The* avenue for reporting bugs is
through ADC.
> My issue is with having to sign up for something that's currently of
> no interest to me, pretend I'm something I'm not, and join the "in
> set" just for the _privilege_ of reporting a bug.
Obviously it *is* of interest to you, because you want to report a bug,
and that's how you do it. It's also of interest to you if you ever
want to program in AppleScript Studio, for that requires Xcode, which
also requires a *free* ADC membership to download or update. (You can
stick with the version that comes with your OS or System and never
update it, but I can't imagine why you'd want to do that).
If you don't want weekly developer news or paid-membership programs,
don't sign up for those. Use the parts you want, like bug reporting
and Xcode, and ignore the other stuff.
If you have a philosophical objection to signing up for anything
labeled "developer" when you're "only" programming in AppleScript, even
though it's free, I don't think I have any words of wisdom for you.
It's like asking why the milk isn't available on the cookie aisle at
the grocer's - because that's not where they put it. They put bug
reporting at <http://bugreport.apple.com/>. That's where it is. It's
not complicated.
If you file the bug, it gets tracked and fixed in a future release. If
you don't, then either someone from Apple like Dave takes his time to
do it for you, or it goes untracked. And I think it is a bug, though
every time I look at what you wrote, I keep thinking, "Wait, there's
some catch, this might be working correctly..."
> set OKNames to {"2.jpg", "03.jpg"}
> tell application "Finder"
> every file of myFolder whose name is in OKNames
> end tell
>
> Files in the folder with names like "2.jpg", "02.jpg", "002.jpg",
> "3.jpg", "03.jpg", "003.jpg", etc are _all_ returned by the above
> reference in Tiger.
..and then I look again and think, "no, I have it backwards." "03.jpg"
is in "003.jpg", but not the other way around. I often get that
backwards on first reading, so I look 2-3X to be sure.
I just tried it, and it works as long as the filename extensions match.
It's like Finder is comparing for integer equality or something, as
any number of leading zeroes matches. ("3E0" does not match "3.0" in a
filename, though that would have been fun, too.)
Can't think of a workaround, either, dangit.
--Matt
--
Matt Deatherage <email@hidden>
GCSF, Incorporated <http://www.macjournals.com>
"It's not like some directories really hold something else, like
pixels, or maybe pudding." -- MDJ 2003.05.22
_______________________________________________
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