Any progress on triggers? For the life of me, I can't figure out how I had previously been able to create new triggers, but I do have some already.
This was before I upgraded to B58. Right now, when I try to create a trigger, it doesn't let me actually create a semantic action to go along with the trigger. Sure, I can define the scope, and the actual keyboard trigger, but when I get to the Commands sub-page, it's just a blank box with an "Edit" button, but there's no way to specify the actual action taken. Any luck for anyone? I'm desperately trying to create a trigger to act as a short cut to invoke an Applescript to "Complete and await reply" assigned to Cmd- Shift-F in the OmniFocus scope. adTHANKSvance, -Mike On Nov 5, 9:31 am, BryanW <[email protected]> wrote: > Thanks for the reply. I'll poke around and see if I'm able to > understand what's going on at all. One question I do have, that might > be fixable if I edit my triggers in an earlier version and save them > is, what command is supposed to be taking place when I invoke the > "Command Window in Text Mode" and "Command Window with Selection" > triggers. My commands are only showing "Execute (null)". Lucky for me, > it is in fact executing null :) . At least it does what it says. > > On Oct 26, 5:28 pm, Patrick Robertson <[email protected]> > wrote: > > > > > > > > > I know, it's annoying. > > > To be honest it shouldn't be too hard to fix since we should be able to use > > git and git bisect good / bad to find which commit actually broke the > > triggers, then change it back (since it was all working before that). > > > Maybe when one of us gets some time we'll be able to fix it. > > > My solutions at the moment are to either: > > > a) Add triggers using an earlier version of QS > > b) Add a triger in b58, open the ~/Library/Application > > Support/Quicksilver/Triggers.plist file BEFORE quitting QS. Save the file, > > then quit QS, then save the file again. Sometimes it takes a couple of > > repeated 'saves' to the file but I can normally get the trigger to stick. > > > I may get some time in the next few weeks, but as usual - nothing's certain! > > > If you want to help, you could learn about git, git bisect and finding a bad > > commit and how to build in Xcode. > > > Basically all you'd be doing is getting git to find which commit broke the > > trigers. You'd do this by checking a commit version by building it in Xcode, > > if it works you tell git it's good (if not you tell git it's bad) then you'l > > hone down to the exact problematic commit. > > > On 27 October 2010 05:27, BryanW <[email protected]> wrote: > > > > I wish I had the knowledge to fix the triggers problem in version ß58 > > > (3841) but unfortunately I don't and I was curious if anybody knew if > > > this was being worked on or if I'm just missing something. Triggers > > > won't save and I can't even invoke QS with a selection or in text- > > > mode. I assume everyone running 3841 has the same problem.
