The 'lost macro' was not part of my KM macros, it still exists on the external disk (SuperDuper- Clone). I got it from (?) years ago, don't remember how it was set on my machine - mysterious.
Great that you came up with this KM macro above ” Replace Spaces with Dashes…” however when selecting a (read & write) file and triggering the macro -> error: Not permitted, Library to Library??
Thank you Chris, I did exactly that but nothing there!
Now I could just wait for JMichaelTX's macro to work (above 4/5), a macro which probably is even better than my old one…
…but I cannot wrap my head around the fact that on the SuperDuper Clone drive there is a working macro (not in KM list) which is working there for ≈ 4 or 5 years 'incognito'!
It has to be somewhere and what is special is that 3 keys are pressed down, and then the 4th key (the dash) is also pressed (video above). This is bugging me.
There should be other people / web designers etc. who use it.
You ran the test when booted from the SuperDuper volume?
Hmm...
The only logical conclusion is that either you're missing seeing the macro in the Keyboard Maestro – OR Keyboard Maestro is not the agent running the macro.
Quit the Keyboard Maestro Engine and try again on the SuperDuper volume.
Also remarkable it's working with 3 keys down + 1 key step bey step: this is not like usual 1 trigger macros. It must be some other script, where could it be stored?
I don't have ForkLift. Are the manual steps to rename a file in FortLift the same as in Finder? If not, could you make an animated GIF to show you doing the rename manually?
@okn thanks for the screenshot, but the reason I asked for:
is so I can see ALL steps you make, including the part where the current name is selected and you type/edit the name.
If you don't know how to make an animated GIF, just do a simple video. You can also search for tools to make it. Here's an example with Finder:
I used SnagIT to create the video and convert to GIF.
This is a very valuable lesson for all to learn in KM. ==Very often the solution to a macro not working correctly is to add or increase the Pause between KM actions== that tell the UI to perform some action for which the KM Action does NOT wait for the app to complete the action.
So when you issue this KM Action:
KM immediately executes the next Action in the Macro, without knowing whether or not ForkLift has completed the "Rename" command.
In this case it had not completed the command, and so the next KM Action, "Copy", copied the file, which translates to the full path of the file.
Placing a short Pause of 0.1 - 0.2 sec allows Forklift to complete the command.
I hope this helps all readers better understand the need for KM Pauses.
@okn and @ccstone, if you guys could test this to make sure it works with ForkLift (post results in the Macro topic) I would greatly appreciate it, since I don't have the ForkLift app.