I was having problems with the "null" thing showing up after closing or restarting triggers, but in my case the particular app I was pointing to wasn't in a folder QS was set to catalog. It was in a subfolder and the cataloging wasn't set to go that many levels deep. So I could search down to find the app to set up the trigger, but it would eventually be lost and turned to "null". Once I set QS to scan the appropriate folder, it hasn't done it since.
On Apr 11, 3:17 pm, ellDov <[email protected]> wrote: > Triggers seems buggy. Particularly adding/changing triggers is > difficult to impossible for me. If I add a custom trigger, sometimes > it works until QS is relaunched at which point the trigger shows up as > "null". Sometimes I'll add a trigger and it won't even work at all. > > The only work around which is occasionally successful is to > directly edit the tiggers.plist. But even the most recent trigger I've > added, and can see in the triggers.plist loads as null when QS > launches.
