LoveQuicksilver - Quicksilver Blog

Quicksilver Improves

Fixes up Triggers, puts advanced features on the mantelpiece, and drops ß62 off at the recycle centre

Users are appreciating the auto updates of Quicksilver and its plugins introduced recently. Unfortunately, a nasty bug in ß61 meant app updates failed to stick, leaving users with the false impression that they were running the latest version. In a few cases, QS ß62 crashing caused custom Catalogs to be deleted and mnemonics to be lost. Thanks to rapid user feedback, we were able to pull the release before many people were affected.

ß63 cannot fix the install bug in ß61, so we ask you to follow Quicksilver’s update instructions to download and install this version from the downloads page. Once installed, the version number in Preferences should read ß63 (3912), and auto updates should work as before.

Let’s take a look around.

Trigger fixes - #85 #174 #240 #248

Triggers are saved properly, can be limited to specified applications (including QS), and remember Objects that aren’t in the Catalog.

Limiting the scope of Triggers to Quicksilver makes it possible to use shortcuts that would be used by other applications, e.g., ⌘L for Quicksilver Selection⇥Large Type.

Applications can also be excluded from Triggers. Image editor Gimp (I don’t know about Photoshop) uses the Windows-style control key modifier for many shortcuts - which QS will override if its Triggers do the same. Once excluded, Gimp can function as normal without Trigger re-assignment.

When creating a Trigger, almost anything can be typed into pane 1 for use as a Trigger’s Object, which QS had an infuriating habit of forgetting if the Object wasn’t in its Catalog. Not so in ß63, which means search URLs can be assigned to Triggers on the fly.

So called ‘advanced features’ are now on all the time - #341 #479

Benefits such as Assign Abbreviation, Extras Preference pane, mouse gestures and browsing Catalog entries from the interface will be available by default.

Proxy objects are enabled by default for new users - #479

Get your hands on Current Selection, Current Document, Computer, Latest Download and many others without digging around in Preferences.
Get the latest

Selection is pulled from any application by default for new users - #479

Grab what you see. Finder Selection is still around for, er, Finder’s selection.

QS will detect if it crashed perviously and offer some actions that might help - #532

While it would be better if this wasn’t necessary, it’s certainly helpful for newer users. One drawback is the crash dialog will appear no matter what the cause was of Quicksilver failing to quit cleanly. An unassociated kernel panic will have QS wringing its hands upon reboot.

Actually, it wasn’t you

Quicksilver can identify (and optionally remove) plug-ins that cause it to crash - #532

Outdated BezelHUD, anyone?

When replacing plug-ins, Quicksilver will no longer remove those inside the application itself (such as Core Support) - #534

Reassuring to know that QS no longer eats itself.

Mouse triggers will continue to work after a restart - #542

The Command builder (the panel used to create/edit Triggers) can be dismissed with ⎋ repeatedly - #537

Stops blank Triggers appearing.

The command builder uses consistent colors to ensure readability - #549

Custom icons for actions in `~/Library/Application Support/Quicksilver/Actions` are displayed in the second pane - #361

Paired with Applescripts that can handle text and files, it’s possible to make Actions that look and feel like fully-fledged plugins.

Lots of possibilities…

Corrected typos in the French localization - #554

Ouvrir.

Prevent a rare crash when loading plug-ins - #561

Respect the preference to NOT check for updates - #560

Users reported that QS still pinged the server to look for updates, even with ‘Check for updates’ disabled.

There’ll be a lot more improvements to Quicksilver in the coming months.

@LoveQuicksilver