Re: Finder f*ck-ups
Re: Finder f*ck-ups
- Subject: Re: Finder f*ck-ups
- From: Martin Orpen <email@hidden>
- Date: Fri, 19 Aug 2005 16:17:36 +0100
On 19 Aug 2005, at 15:33, John C. Welch wrote:
Oh really...straw men?
Let's see, what's the title of your post?
Why, "Finder F*ck-ups". No, no insinuation there. None at all.
That's a pretty accurate description of what was happening to my
script and then verified by dragging files in the Finder.
The lead sentence in *your* original post:
" What's going on with the Finder in Tiger?"
That's a question - not an *insistance*.
Hmm...no, no insinuation about the Finder at all. You then go on to
talk
about stuff that has very little to do with the finder outside of this
quote:
" I've got no problem with *copy protection* but having files
disappear
from the Finder windows indicates some pretty pathetic programming
from
Apple."
No, no, not disparaging the Finder team at all. Not even close.
Especially
when that has little to do with the behavior you're reporting.
(This happens
on pooched automounts all the time, so I pretty much can guarantee the
disappearing files are not exclusive to the DVD issue.)
Dave Lyons - who actually works on the Finder wrote:
The part about the items later disappearing from Finder is
certainly a bug; I believe it's already covered by <rdar://problem/
3949358>.
John continues:
Then in almost every single example of what you tried, you show
that it's
pretty obviously not a Finder bug, but at NO point do you say
"Well, it
looks like the title of this post was incorrect and misleading, as
it's
obviously not a Finder bug", because hey, once you get started
beating the
Finder team, stopping is so dull, because slapping the Finder team
is what
all the kewl OS X kidz are doing.
Whereas I'd already written:
Obviously, the fact that most people will encounter this problem
while using
or scripting the Finder does not mean that the Finder is to blame.
And already called your attention to it.
But don't let what people have *actually* written get in the way of
your obsession with having the *final and definitive word* on any
subject.
The bug report has been filed. The probable reason isolated. People
have been warned of something that might cause their scripts to not
work as expected.
And we've all been reminded that the ability to post the most
authoritative answer on *every* programming issue seems to be
inversely proportional to the amount of lines of AppleScript that you
actually write or post to this list.
Bye.
--
Martin Orpen
_______________________________________________
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