Thanks for clarifying Fredrik, that does sound really cool! Probably not going to happen for 3.0 but I can keep it in mind for later.
@redsweater, fingers crossed… 
In mean time here is example of a user how have take it to next level
and use midi to do it. It will give you some ideas what is possible.
And with ideas from Sensel we could have custom layouts for touch device that could communicate with a mac.
Trackpad or any touch device is truly powerful and useful.
Hi @ionah - thanks again for this feedback. I wanted to let you know that in the latest FastScripts 3.0 beta (3.0b38), I’ve addressed this issue. You should be able to invoke scripts that were freshly added since the last time the FS menu icon was clicked, and conversely, you will no longer be able to invoke a script that was since removed. FastScripts now dynamically updates the scripts at the portion of the script hierarchy where you are trying to invoke. Let me know if you spot any other issues!
Hi @redsweater
That’s great!
Unfortunately, I will not be able to send you feedback on it, as I’m stuck on High Sierra: I can’t find the time to make the update.
I hope I will be back in a couple of weeks with a brand new Catalina installed.
Cool, thanks for letting me know. It will be waiting for you when you eventually get a chance to update.
Daniel @redsweater, I had to quit the FastScripts beta, and on relaunch it now says the pre-release copy has expired. I still have my FastScripts 2 license, but wanted to let you know. FYI, the dialog about expiration references MarsEdit, not FastScripts.
Ah, sorry about that! The latest version is 3.0b41 which shouldn’t expire until May 9. You can download a fresh copy here:
https://redsweater.com/fastscripts/FastScriptsBeta.zip
Thanks for noticing the mistake referencing MarsEdit instead of FastScripts! I’ll get that fixed.
Hey folks - I am getting closer to finishing up 3.0 but have a few more loose ends to tie up. Today I’ve just posted another beta update, 3.0b42. You can “Check for Updates” if you’re already running a 3.0 beta, or download a fresh copy here:
https://redsweater.com/fastscripts/FastScriptsBeta.zip
The main change in this update is a new behavior to automatically focus on the first search result and to invoke it if you press return. This means you can now activate FastScripts, type a search term, and press return to invoke whatever the first match is. Kind of handy for things you know you will invoke often.
Folks who are enjoying the beta may have run up against an expiring beta. I let the last beta expire and didn’t get the newer version out until the very day of the expiration. If you are already running a FastScripts 3 beta you should be able to get the latest by selecting Check for Update within the app’s preferences. Otherwise you can download an updated beta here:
https://redsweater.com/fastscripts/FastScriptsBeta.zip
I hope to get 3.0 finalized in the next month or two!
Daniel
Hi Daniel,
Does FastScripts 3 sync between Macs i.e. will it sync the keyboard shortcuts I create for FS on each Mac? If so, how will it handle the situation where I frustratingly have a different username on each Mac so the file paths to scripts will be the same if it begins with a ~/ but different if written out in full from /Users/?
Unfortunately FastScripts doesn’t do any syncing of scripts or shortcuts on its own, but if you do export/imporpt the preferences from one Mac to another, the keyboard shortcuts should resolve for the respective scripts as long as they are in the same relative location of each script folder. FastScripts doesn’t hard code the full path using the user name, but stores the scripts as relative paths from the script folder they are in.
Okay, good to know about the relative paths, thanks.
Can I request syncing for FastScripts 4.0? I have a work Mac and a – um, I guess – play Mac and I love stuff that syncs between them. I’ve got the paid version of FastScripts 2 and I also use Keyboard Maestro for executing scripts. Generally I prefer FastScripts for executing scripts as it’s way simpler and easier and more targeted to just that task, but I do have a bunch of scripts and keyboard shortcuts set up in KM from before I knew about FS. THE OCD ocdopus in my brain tells me to move all those scripts from KM to FS for consistency and purity etc, but the practical side of my brain tells me not to waste time tinkering with things that already work. But one other reason KM works well for executing scripts is that they sync across multiple Macs by saving your preferences file in Dropbox. It’s nice when (as I had to do recently) I need to update the script and shortcut on one Mac it automatically syncs on the other.
And another feature request for FastScripts 3 (maybe version 3.1 if you like) – could you please add a GUI for adding/changing the scripts folders that FS looks at? I prefer to keep my scripts in Dropbox so again they sync etc. I know there’s the way to change it using defaults write and I’ll also look at using symlinks but I think a GUI to manage the scripts folder would be great. In fact now I think of it perhaps you’ve already done this so I should probably go download the beta. 
If you want to build your own syncing system, and not deal with the preference file, take a look at the FastScripts dictionary:
script item
keyboard shortcut get/set key combination The key combination assigned as the shortcut for this script, if any.
Can you not set your FastScripts library to be stored in Dropbox ?
Actually, I’d go with you initial gut that was cajoling you to centralise your scripts to a single location that can be sourced by whatever program needs it. I did this before, and intend to again when I set up properly. I seem to remember Fast Scripts was fine with my custom folder path.
I can, but I almost exclusively use FastScripts to trigger scripts with a keyboard shortcut. And from what I know so far I don’t think that FastScripts fully supports syncing your keyboard shortcuts across multiple Macs.
Hey Folks,
Does anyone have a copy of FastScripts 3.0b46 (1377)?
Daniel updated it to v3.0b52 and broke FastScripts’ accessibility in Mojave. I’ve emailed him but haven’t heard back.
Like a fool I hit [Update] before making sure I had a viable backup of the old version, and now my workflow is pretty severely afflicted.
I don’t want to back up all the way to v2.8.3 without knowing if it’s entirely compatible with v3.x, but I might have to back up settings and do so anyway if I can’t get my hands on v3.0b46 right quick.
TIA.
-Chris
I’ve followed up with Chris via email, but I thought I would also post here in case anybody else is in a similar situation.
I can’t think of why the 3.0b52 update would cause problems specifically with accessibility authorization, but what’s most significant about the 3.0b51/52 updates is that they changed the bundle identifier from com.red-sweater.fastscripts to com.red-sweater.fastscripts3. This means that the system is probably going to prompt again to ask permissions for all the usual things. But I don’t think it should be any more likely to fail than the earlier versions.
For Chris and anybody else who runs into this and think that downgrading might help, I recommend downgrading to 3.0b50. Since the versions are all auto-expiring in beta, this will be the longest-lived version of the beta that still has the older bundle ID. You can download it here:
https://redsweater.com/fastscripts/FastScripts3.0b50.zip
On that note, the download pattern is pretty predictable so generally if you feel you need to download a previous version you can guess the URL based on that format.
Daniel
1 Like
I’m up and running again and appreciate Daniel’s timely help.
It’s amazing how fast your world can go to hell in a hand basket when your tools break…
-Chris
2 Likes
It’s amazing how quickly we can get help from developers like Mark and Daniel. Small third-party developers really are the best!
4 Likes
Hi Ray - following up on this old feedback, I wanted to let you know that in FastScripts 3.0.6, which I just released, there is now access to the “script tasks” of the app via FastScripts’s own scripting dictionary… So if you wanted to set up a script to terminate a running script you should be able to do that now with a custom script for that purpose.
3 Likes