Hello @DanThomas, I have problems with the action "Add Action(s)".
On my iMac with macOS Catalina (10.15.7) and KM (9.2) the action works fine.
On my MacBook running macOS Big Sur (11.4) with KM (9.2), I get a hint sound after triggering (F5) like a shortcut I've already used and then I get a hint to select an action.
The sound is just something I play when there's an error. I don't know what's causing the error, because you're obviously selecting an action. It tries to copy the selected action to the clipboard, then gets it off the clipboard. For some reason, it looks like the action isn't getting copied to the clipboard. No idea why.
You need to move it to a folder outside of Downloads. Make a new folder on your desktop, and drag the installer there. Then run it from that new folder. That should fix it (knock on wood). If you're running Big Sur, you may have other issues. Let me know.
Please add the "Display Text in a Window" as shown. The text in the window is:
%Variable%kmfamSelectData%
Then press F15, and let me know what the window shows.
Also, in the KMFAM Resources folder (wherever you put it and whatever you named it - if you can't remember, look at this variable: DND__kmfamResourcesFolderPath ), there's a file named "FavoriteActions.json ":
Can you zip "FavoriteActions.json " and post it here in a reply?
The 01)KMFAM Select (insert action) one doesn't work.
The 02)[KMFAM] Select or Switch to Insert Action by Name works. No big deal, can use the 02) one.
Thanks for taking the time to write those instructions, but a simple delete and reinstall got it up and running. I'll stay on 1.1 for now, as it seems to be working ok.
I've got a suite of macros that manage window placement. Though they are only 85% complete, they are better than anything else I have seen here. However:
I don't really have the time to document them fully
I certainly don't have the time that Dan has to provide after-release support
So let's appreciate Dan for being..better than I am.
I get that, totally. I'm the same way. I have a lot of macros that would probably be useful to people, but documenting them is often harder than writing them!
That's really the big issue, isn't it? I have a ton of Final Cut macros that really streamline my workflow. But if I released them, and people built their workflows around them, what happens when something changes in Final Cut that breaks them? People are stuck, and I'd feel like I have to solve the problems. Not worth it.
It's only worth it when the macros are simple, or really, really helpful, and I can feel like they'll hold up to future changes pretty well.
Well, I'm retired, so maybe that has something to do with my being willing to do some of this stuff.