Re: Using Applescript Droplet as Default Application? (10.4.11)
Re: Using Applescript Droplet as Default Application? (10.4.11)
- Subject: Re: Using Applescript Droplet as Default Application? (10.4.11)
- From: Eric Taylor <email@hidden>
- Date: Mon, 19 Jan 2009 11:08:36 -0700
Hi again list,
OK, thanks to everyone for their replies. I decided to just let the
issue cool over the weekend as it was getting pretty frustrating. Hit
it fresh on Monday and delved into the lsregister command. It turns
out there is a "-lint" option which is wonderfully useful!
/System/Library/Frameworks/ApplicationServices.framework/Versions/A/
Frameworks/LaunchServices.framework/Versions/A/Support/lsregister -
kill -lint -f -v /xxx/yyy/zzz.app
will refresh the db and also tell you if there are any issues, which
mine indeed had!
*** Error(s) found while registering path /xxx/yyy/zzz.app:
Signature mismatch: PkgInfo signature = 'dplt', plist
CFBundleSignature = '????'
So the initial recipe provided by JJ was correct in all particulars
except that step 3 needs one additional substep. Whatever you change
the BundleSignature to needs to be matched in the PkgInfo file too.
PkgInfo starts out as APPLdplt after saving an applescript bundle and
the 'dplt' part needs to be updated with whatever you chose as your
signature.
I just ended up changing mine to '????', which means it is supposed
to work for all file types according to the dev notes.
At any rate, I can now successfully "Get Info" and "Change All" to
use my Opener script.
Thanks again for all the help and suggestions!
Eric.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
AppleScript-Users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
Archives: http://lists.apple.com/archives/applescript-users
This email sent to email@hidden