You asked how to get rid of it altogether, not to replace it.
Freeway will always try to use the latest version of any Action you have defined, looking in the following locations in this order: the current user’s Actions folder, the System-level Actions folder (in /Library/Application Support – note the preceding slash, this goes all the way to the root of your drive), the Freeway application bundle, and finally, the document itself.
Adding a new version of an existing Action should give you a dialog asking if you want to install an Action that replaces an existing Action.
Lots of things can trip this up. You may have downloaded both of the Actions within a short period of time, and not cleaned out your Downloads folder in the interim. So Finder will have renamed the second file, adding a -1 or -2 or whatever to deal with the duplicate file path. Since the replacement Action file has a different filename, Freeway might not notice that you’re adding a newer version of an existing Action. Another thing that could make this not work is if the two files’ modification dates are in the opposite order than you might expect – the newer one is “older” on disk. Finally, if the internals of the two Actions are different, but have the same tag inside them, that might be another point of confusion.
If you look in the Edit / Actions dialog, you will see a nested list of all Actions, with the nesting indicating where they are installed. If you open this dialog within a document that is running an Action from the document’s cache, you will see that Action pulled out separately from the others in the list. I don’t recall exactly what is written around it, but it is noted as being sourced from the document.
Bundled Actions (Actions that have multiple files concealed inside a special directory structure that appears to be a single file in the Finder) have a special problem with running from the cache – they rely on separate files being located at specific offsets from the path of the Action itself, and when run from the cache, those file paths are completely non-existent. This is why you’ll see me rail on about how to entirely remove an Action from your document before updating to a newer version. In the case of the CSS3 Shadow Action, that shouldn’t be an issue, but for other more complex Actions, you will see this issue raise its ugly head.
Walter
On Sep 11, 2013, at 12:30 PM, Robert wrote:
Walter,
If I understand you correctly, it would appear that an updated action doesn’t really update an existing document as the cached copy will always be relied upon. To have to go and undo then redo every instance of an action seems like it takes one back to the 1980s programming!
I understand manually removing and installing actions (and yes, I’m on Mt. Lion). Wouldn’t Freeway look for the action and then simply use the updated version?
Robert
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options