Finder broken
Finder broken
- Subject: Finder broken
- From: Paul Berkowitz <email@hidden>
- Date: Thu, 29 Jul 2004 14:49:59 -0700
Something that was rife in both OS 9.2 and 10.1, seemed to be fixed in 10.2,
appears to be back again in 10.3, also much less prevalent.
I have had a few users - maybe 10 by now - whose Finder is not scriptable.
No aete. No matter what the command, they get an error that the Finder can't
get <<whatever>>, always raw code. Re-launching the Finder, rebooting,
repairing disk permissions. Nothing seems to help. (It never occurred to me
to suggest Disk Warrior.) The only that works is to reinstall OS 10.3 and do
the updates.
This is nor satisfactory, even if the numbers are quite small. Has anyone
seen this, and have you found some way to fix it, prod it, whatever?
Fortunately, there are a lot of Finder commands that can be done now,
probably better, by System Events. But one of the most important
application file id "xxxx"
cannot. That one is very important for being able to find the application
file of a 3rd-party app that may not be open, so that a variable can be set
to the text path of the application file and yell blocks directed to the
'application variable ' , perhaps with a ''using terms block' if more needs
to be done than just launching it, without the dreaded "Where is ?" dialog.
I would have thought that this would be right up System Event's alley but -
no, it doesn't know anything about application file id. I hope it eventually
learns.
So, does anyone know how to fix the Finder's missing aete, other than an OS
reinstall?
--
Paul Berkowitz
_______________________________________________
applescript-users mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/applescript-users
Do not post admin requests to the list. They will be ignored.