quicksilver/Quicksilver — pull request #1650 by skurfer (2013-10-15 17:00:51+00:00)
Title: Trigger bugs

A couple of one-liners to restore my sanity.

This has bothered me for a looooong time: Open the settings for a trigger and try to edit the name/description at the top. :rage:

I was running into something similar with the delay setting in Event Triggers and finally tracked it down.

First, when setting up the view, it would always get the first trigger in your prefs instead of the trigger you were viewing. So the settings view for every trigger was treated like a settings view for hotkey triggers (in my case). The first commit fixes this for all non-hotkey triggers.

But you still couldn't edit the name for a hotkey trigger because, for some reason, other text fields in that view were being treated as hotkey capturing thingies™. The second commit enables that behavior only for instances of `QSHotKeyField`. I neither find, nor imagine what that might break.