It's hard to say why the triggers are acting this way for you. Having
just "fixed" the trigger code for SN, I have a couple suspensions
about the cause, but not a work around a user could use. Though it's
probably not related, the trigger info is not saved until 10 seconds
after the change is made. So if you quit or restart QS within 10
seconds of making a trigger change, the change is lost. This isn't
what you describe though. I suspect the problem is with the code and
trigger handles, but this is hard to confirm because I didn't write
the original code and don't know what the author intended, it's pretty
much just based on observations while fixing/debugging another trigger
issue.
A thought just occurred for a possible work around, you can check
~/Library/Application Support/Quicksilver/Triggers.plist
it is in an XML format so open it with a good editor. Find the <dict>
entry for your trigger, and make sure the enabled key is set to true -
here's an example of the Get IP script done as a ctrl A trigger from
that file. See the <key>enabled</key><true/> section? Make sure yours
has that set. Let us know if that helps.
Thanks,
Paul
<dict>
<key>ID</key>
<string>ED929E0B-8941-4EB6-8F08-68720B818102</string>
<key>command</key>
<dict>
<key>actionID</key>
<string>AppleScriptRunAction</string>
<key>directID</key>
<string>~/Library/Application
Support/Quicksilver/PlugIns/Extra
Scripts.qsplugin/Contents/Resources/ExtraScripts/Networking/Get
IP.scpt</string>
</dict>
<key>enabled</key>
<true/>
<key>keyCode</key>
<integer>0</integer>
<key>modifiers</key>
<integer>262401</integer>
<key>onPress</key>
<true/>
<key>type</key>
<string>QSHotKeyTrigger</string>
</dict>
To unsubscribe from this group, send email to
blacktree-quicksilver+unsubscribegooglegroups.com or reply to this email with
the words "REMOVE ME" as the subject.
