If this is just a b58 thing how about swapping it temporarily with b57 just to set up the trigger? That is, using the same set of Application Support folders/files for b57 and b58. Once you're sure it's stuck you can then swap b58 back and hopefully it'll stay stuck. Maybe.
On Apr 13, 12:11 am, tuniTMF <norm...@gmail.com> wrote: > tried the "temporary" solution - using Snow Leopard. on restart still > get "null" where the set up trigger should be. <sigh> > It shouldn't be this difficult - we are missing > something.....somewhere....would really like to get this trigger > problem solved. :( > tuni > > On Apr 12, 3:28 pm, Patrick Robertson <robertson.patr...@gmail.com> > wrote: > > > > > I've seen this problem. > > > The current - temporary solution seems to be > > > a) Change the triggers as required > > b) Open ~/Library/Application Support/Quicksilver/Triggers.plist (keep it > > open) > > c) Quit Quicksilver > > d) Save the Triggers.plist file and close > > e) Relaunch Quicksilver > > > This bug may have been introduced in b58 as a few trigger related things > > were changed there. > > > On 12 April 2010 20:15, tuniTMF <norm...@gmail.com> wrote:> whatever it is, > > there are several of us having the same problem. am > > > still working on it...too > > > > On Apr 12, 4:28 am, lloyd709 <lloyd...@btopenworld.com> wrote: > > > > I'm trying to set up a simple trigger to open a folder. It works up > > > > until I quite and re-start Quicksilver when the trigger reads 'Open > > > > (null). > > > > > Anyone know what the problem is? -- To unsubscribe, reply using "remove me" as the subject.
