So if you've been trying and trying to create a trigger for QS, and i
keeps forgetting your hotkey combos, like me, there is another
option...
You can edit the triggers.plist file yourself. All the preference
setting is doing is essentially writing some text into a text file in
a certain syntax. While I wouldn't recommend creating a new trigger
from scratch, if you're just having an issue getting QS to remember
the keyboard shortcut you want for the trigger, this seems to work for
me:
instructions:
1. Back up your triggers.plist. It's in ~/Library/Application Support/
Quicksilver. If you've made a trigger before it should exist. I'm not
sure it does if you've just installed a QS (in which case there are no
triggers to back up)...
2. Open QS' preferences and make a trigger.
3. leave QS' preferences open, and go to your triggers.plist file and
open it with either PlistEditPro, TextMate, TextEdit. TextEdit would
be fine.
4. Once open, type command-f and search for the trigger you just made
by name. So if you just made a trigger to run an applescript named
FiWi.scpt, search for FiWi.scpt. Or an itunes trigger to play/pause
search for play/pause.
5. Once found, the whole trigger should begin with <dict> and end with
</dict> and look like this:
<dict>
<key>ID</key>
<string>7DC60882-CA49-4373-ABE3-FF5533BF5A13</string>
<key>command</key>
<dict>
<key>actionID</key>
<string>AppleScriptRunAction</string>
<key>directID</key>
<string>/Users/Elspub/Library/Scripts/allClip.scpt</string>
</dict>
<key>enabled</key>
<true/>
<key>keyCode</key>
<integer>14</integer>
<key>modifiers</key>
<integer>262401</integer>
<key>onPress</key>
<true/>
<key>type</key>
<string>QSHotKeyTrigger</string>
</dict>
6. There are three lines here that are important for us. Up in the
inner "<dict>" is a string (or line of text) which points to our
script by path. In this case "/Users/Elspub/Library/Scripts/
allClip.scpt". Then there's the keyboard shortcut, notated by keyCode
(here it's the integer 14, which refers to the "w" key), and modifiers
(which here is the number 262401, which refers to the control key).
7. Copy your trigger and paste it into a another text file. Actually
copy your trigger along with the trigger before and after it, just so
we know "where it goes" in the order of the triggers.plist.
8. Quit the triggers.plist and Quicksilver (at this point we've only
copied some info out of the plist, so if, for some reason, TextEdit
asks to save it before quitting, click no).
9. Reopen your trigger.plist, with QS quit, and search for your
trigger. You can now look and see if any of that information has been
mysteriously deleted, which QS seems to do somewhere between creating
a trigger and relaunching the first time after you've made the
trigger.
10. Take look. Are those three pieces of info the same? Since you've
copied the trigger to you can compare the before and after quitting QS
versions of the trigger. if anything's changed just fix it. Save the
triggers.plist. And close it.
11. Reopen QS, open preferences. Did it work? Seems to, for me. If not
repeat steps 8 - 11 until it does.
12. If, you're trying to delete a trigger, instead of create one,
which can be just as troublesome, all you have to do is open your
triggers.plist search for the trigger and delete its entire entry,
everything from <dict> thru </dict>
Once you've successfully created a trigger that lasts across
relaunching of QS it should last. Back up your new triggers.plist
file. If your triggers go missing again you can always swap in your
backup...
A final note. If you end up editing your triggers file in anyway, I
would stay away from editing anything other than the three pieces of
information I mention in step 6, or deleting a trigger.
happy triggering
