b137: Workflow updating & bundle IDs

[Vero]

We have just put out b137, which brings workflow updating and a few other improvements.

 

Here's what's new:

• Hotkeys: When importing a workflow, hotkeys are stripped for your safety so you'll need to set these to a hotkey of your choice.
• Workflow updating: Bundle IDs are now meaningful, as these indicate to Alfred which workflow to replace when you import an update to one of your existing workflows. You'll see a notice in red telling you which workflow will be replaced.

Enjoy the latest build

[Andrew]

It's worth also adding to this that in the not too distant future, I am going to look at adding hotkey and keyword migration to the workflow updating, which means that if you setup a workflow to your liking, the keywords and hotkeys will remain through an upgrade.

[ctwise]

It's worth also adding to this that in the not too distant future, I am going to look at adding hotkey and keyword migration to the workflow updating, which means that if you setup a workflow to your liking, the keywords and hotkeys will remain through an upgrade.

 

Could it be possible to just add the capability to disable hotkeys instead? So instead of blanking them on import, just disable them. Then the user can decide to enable them or change them at their discretion. Otherwise the user has to go through the readme or other documentation to figure out what the workflow writer thought would work best.

[Andrew]

Could it be possible to just add the capability to disable hotkeys instead? So instead of blanking them on import, just disable them. Then the user can decide to enable them or change them at their discretion. Otherwise the user has to go through the readme or other documentation to figure out what the workflow writer thought would work best.

 

No, because the other benefit of just stripping the hotkey is that it avoids duplicate hotkeys which may already be set by another workflow or set by another completely separate application on your Mac.