Is Finder "update" command broken in OSX?
Is Finder "update" command broken in OSX?
- Subject: Is Finder "update" command broken in OSX?
- From: Cornwall <email@hidden>
- Date: Sat, 27 Apr 2002 15:49:42 -0700
Back at the beginning of the month, I asked how to force the Finder to
update the contents of a folder whose files were being rewritten by a
console app. Several replies suggested the Finder's "update" command
should cause the Finder to "see" the new files.
"Update" doesn't work. It still seems that nothing short of opening the
folder's window, logging out and back in or restarting the machine will
make the Finder recognize the new files.
Anyone who has the "Folding@home" v2 console app can demonstrate this
behavior with the script below. The script will work up until the files
get rewritten and then error. Opening the "work" folder window,
restarting etc. will get the script going again. I tried: update alias
"folder:path:", update folder "folder:path:", update every file of
alias "folder:path:", update contents of alias "folder:path:", and so
forth until I was blue in the face.
tell application "Finder"
try
set fil1 to first file of folder ,
"HD:Users:me:Folding1:work:" whose name contains "logfile_"
fil1 as alias returning als1
on error
update alias "HD:Users:me:Folding1:work:"
-- and every other construction I could think of
set fil1 to first file of folder ,
"HD:Users:me:Folding1:work:" whose name contains "logfile_"
fil1 as alias returning als1
end try
end tell
tell application "TextEdit"
activate
open fil1
end tell
Thanks
Corny
_______________________________________________
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.